You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Branch Cleanup's workflow_dispatch and push-sentinel trigger paths no longer offer a stale batch option that branch-cleanup-delete.sh cannot execute. Both trigger paths now only expose safe/review, matching what the script (and docs/branch-cleanup-matrix.csv, which has no STALE verdict) actually supports.
Scope
Included:
.github/workflows/branch-cleanup.yml: removed stale from workflow_dispatch.inputs.batch.options, from the push-sentinel grep/sed regex, and from the header comment documenting the sentinel syntax.
Explicitly excluded:
No changes to scripts/maintenance/branch-cleanup-delete.sh (safe/review logic untouched).
No changes to the branch verdict matrix or audit data.
Risk
Risk level: low
Failure mode: none expected — stale was never a working option; removing it only prevents users from selecting an input that always failed.
Rollback: revert this commit.
Verification
Reproduced the failure signature from the real failing run: usage: scripts/maintenance/branch-cleanup-delete.sh {safe|review} / exit 2, confirming stale was unimplemented.
grep -n "stale" .github/workflows/branch-cleanup.yml → no matches remain.
Simulated sentinel regex logic: [run-cleanup:safe] still matches and extracts batch=safe; [run-cleanup:stale] is now correctly rejected instead of reaching the script.
DRY_RUN=1 scripts/maintenance/branch-cleanup-delete.sh safe → exits 0, unaffected by this change.
Production evidence
Not applicable — CI/workflow-definition-only change; no runtime or deploy impact.
Agent handoff
One canonical issue is linked
No competing PR implements the same issue
Acceptance criteria are satisfied (unimplemented option removed from both trigger paths)
Required checks pass on the current head
Human decision is requested only for product, security, irreversible infrastructure, or production approval
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 1
Caution
Protected files were modified in this change.
This pull request is in
request_reviewmode and requires explicit human scrutiny before merge.Protected files:
.github/workflows/branch-cleanup.ymlCanonical issue
Canonical issue: “Branch Cleanup workflow_dispatch batch=stale always fails (exit 2)” (created alongside this PR).
Outcome
Branch Cleanup'sworkflow_dispatchand push-sentinel trigger paths no longer offer astalebatch option thatbranch-cleanup-delete.shcannot execute. Both trigger paths now only exposesafe/review, matching what the script (anddocs/branch-cleanup-matrix.csv, which has noSTALEverdict) actually supports.Scope
.github/workflows/branch-cleanup.yml: removedstalefromworkflow_dispatch.inputs.batch.options, from the push-sentinelgrep/sedregex, and from the header comment documenting the sentinel syntax.scripts/maintenance/branch-cleanup-delete.sh(safe/reviewlogic untouched).Risk
stalewas never a working option; removing it only prevents users from selecting an input that always failed.Verification
usage: scripts/maintenance/branch-cleanup-delete.sh {safe|review}/ exit 2, confirmingstalewas unimplemented.python3 -c "import yaml; yaml.safe_load(open('.github/workflows/branch-cleanup.yml'))"→ parses cleanly.grep -n "stale" .github/workflows/branch-cleanup.yml→ no matches remain.[run-cleanup:safe]still matches and extractsbatch=safe;[run-cleanup:stale]is now correctly rejected instead of reaching the script.DRY_RUN=1 scripts/maintenance/branch-cleanup-delete.sh safe→ exits 0, unaffected by this change.Production evidence
Not applicable — CI/workflow-definition-only change; no runtime or deploy impact.
Agent handoff
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 1
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.Create the pull request manually