Skip to content

ci(auto-merge): correct the reason this repo passes a PAT - #49

Merged
github-actions[bot] merged 1 commit into
mainfrom
ci/pat-rationale
Sep 7, 2026
Merged

ci(auto-merge): correct the reason this repo passes a PAT#49
github-actions[bot] merged 1 commit into
mainfrom
ci/pat-rationale

Conversation

@catomean

@catomean catomean commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

The comment added a few hours ago claims GITHUB_TOKEN cannot merge a PR that touches .github/workflows. That is contradicted by this fleet's own history.

github-actions[bot] merged datacat#253 and ai-kit#42 today. Both change a workflow file.

I asserted it from the reusable workflow's docstring without checking, then found the counter-evidence while looking for something else.

The two "stalled PRs" I cited don't survive either

PR What I said What's true
ai-kit#11 stalled 9 days because the token couldn't merge it opened 2026-08-29; that repo's sweep wasn't added until 2026-09-04. Nothing was sweeping for most of its life.
aoz-housing#122 same Still unexplained — I merged it before diagnosing it, which destroyed the evidence.

Why the line stays

The throughput reason is unaffected, and it's the one that matters.

A dispatch made with GITHUB_TOKEN triggers no workflows — the same rule the deploy reconciler exists for. So after the sweep merges a PR and re-arms CI, that CI run's completion fires no workflow_run, and nothing wakes the sweep to take the next PR. It waits for the cron, which GitHub throttles regardless of what the cron says: fleetcrown's sweeps land 50–65 minutes apart against a */10 schedule. A PAT-created dispatch does emit workflow_run, so the queue drains at CI speed.

The wrong claim is recorded in the file rather than quietly deleted, so the next reader doesn't re-derive it from the same docstring I did.

No behaviour change: an undefined secret still resolves to empty, and the reusable workflow still falls back to github.token.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P

The comment added a few hours ago says GITHUB_TOKEN cannot merge a PR that
touches .github/workflows. That is contradicted by this fleet's own history:
github-actions[bot] merged datacat#253 and ai-kit#42 today, and both change a
workflow file. I asserted it from the reusable workflow's docstring without
checking, then found the counter-evidence while looking for something else.

Two stalled PRs were offered as proof and neither survives either. ai-kit#11
opened 2026-08-29 and this repo's sweep was not added until 2026-09-04, so for
most of that PR's life nothing was sweeping at all. aoz-housing#122 is still
unexplained — I merged it before diagnosing it, which destroyed the evidence.

The THROUGHPUT reason is unaffected and is why the line stays. A dispatch made
with GITHUB_TOKEN triggers no workflows — the same rule the deploy reconciler
exists for — so after a merge the re-armed CI run's completion fires no
workflow_run and nothing wakes the sweep for the next PR. It waits for the
cron, which GitHub throttles: fleetcrown's sweeps land 50-65 minutes apart
against a */10 schedule. A PAT-created dispatch does emit workflow_run.

The wrong claim is recorded in the file rather than quietly deleted, so the
next reader does not re-derive it from the same docstring I did.

No behaviour change: an undefined secret still resolves to empty and the
reusable workflow still falls back to github.token.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P
@github-actions
github-actions Bot merged commit 78fcd76 into main Sep 7, 2026
1 check passed
@github-actions
github-actions Bot deleted the ci/pat-rationale branch September 7, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant