Autonomy / Atomicity Findings
1. Agent Deep Dive auto-selection only reaches the first seven sorted workflows
Category: Ordering dependency
File(s): .github/workflows/agent-deep-dive.md
Problem: The daily auto-selection is based only on day-of-week. The workflow builds a sorted list of matching workflow files, but then computes the index as IDX=$(( (DAY - 1) % COUNT )) where DAY=$(date +%u). Because DAY is always 1-7, repositories with more than seven matching workflows can only select indexes 0-6 on scheduled runs.
Evidence:
.github/workflows/agent-deep-dive.md:18-19 schedules the workflow on weekdays.
.github/workflows/agent-deep-dive.md:79-82 builds the sorted WORKFLOWS list from paths matching trigger-|gh-aw-.
.github/workflows/agent-deep-dive.md:89-91 selects TARGET_WORKFLOW using only the weekday-derived index.
- Local verification found 93 matching
.github/workflows files. The first eight sorted entries are gh-aw-agent-suggestions.lock.yml, gh-aw-autonomy-atomicity-analyzer.lock.yml, gh-aw-branch-actions-detective.lock.yml, gh-aw-breaking-change-detect.lock.yml, gh-aw-breaking-change-detector.lock.yml, gh-aw-bug-hunter.lock.yml, gh-aw-code-complexity-detector.lock.yml, and gh-aw-code-duplication-detector.lock.yml; index 7 and later are unreachable by the scheduled rotation.
Suggested fix: Use a rotation value whose range grows over time, such as day-of-year or github.run_number modulo COUNT, or persist/derive a least-recently-analyzed workflow. If the intent is to analyze only trigger workflows, narrow the filter explicitly before rotating.
Suggested Actions
What is this? | From workflow: Trigger Autonomy Atomicity Analyzer
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Autonomy / Atomicity Findings
1. Agent Deep Dive auto-selection only reaches the first seven sorted workflows
Category: Ordering dependency
File(s):
.github/workflows/agent-deep-dive.mdProblem: The daily auto-selection is based only on day-of-week. The workflow builds a sorted list of matching workflow files, but then computes the index as
IDX=$(( (DAY - 1) % COUNT ))whereDAY=$(date +%u). BecauseDAYis always 1-7, repositories with more than seven matching workflows can only select indexes 0-6 on scheduled runs.Evidence:
.github/workflows/agent-deep-dive.md:18-19schedules the workflow on weekdays..github/workflows/agent-deep-dive.md:79-82builds the sortedWORKFLOWSlist from paths matchingtrigger-|gh-aw-..github/workflows/agent-deep-dive.md:89-91selectsTARGET_WORKFLOWusing only the weekday-derived index..github/workflowsfiles. The first eight sorted entries aregh-aw-agent-suggestions.lock.yml,gh-aw-autonomy-atomicity-analyzer.lock.yml,gh-aw-branch-actions-detective.lock.yml,gh-aw-breaking-change-detect.lock.yml,gh-aw-breaking-change-detector.lock.yml,gh-aw-bug-hunter.lock.yml,gh-aw-code-complexity-detector.lock.yml, andgh-aw-code-duplication-detector.lock.yml; index 7 and later are unreachable by the scheduled rotation.Suggested fix: Use a rotation value whose range grows over time, such as day-of-year or
github.run_numbermoduloCOUNT, or persist/derive a least-recently-analyzed workflow. If the intent is to analyze only trigger workflows, narrow the filter explicitly before rotating.Suggested Actions
WORKFLOWS.COUNT > 7and verifies auto-selection can cover indexes beyond 6.gh-aw-*.lock.ymlworkflows should be eligible; if not, filter the candidate list to triggers only before selection.What is this? | From workflow: Trigger Autonomy Atomicity Analyzer
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.