fix(ci): auto-merge points at an owner that no longer exists - #789
Merged
Conversation
Nothing has merged or deployed since the GitHub account was renamed from
`maonakamoto` to `catomean`. Every auto-merge run since fails before it
starts, with "This run likely failed because of a workflow file issue"
and no log to read.
uses: maonakamoto/dotfiles/.github/workflows/auto-merge-sweep.yml@master
GitHub redirects a renamed owner for the REST API and for git remotes —
`gh api repos/maonakamoto/dotfiles` still answers, which is exactly what
makes this hard to see — but the Actions resolver does NOT follow the
redirect when loading a reusable workflow. It looks for an owner that is
not there any more and fails the whole run before any step exists.
The failure mode is the bad one this file's own header warns about, from
the other direction: a green PR that GitHub reports as CLEAN and
MERGEABLE, no red check anywhere on it, and nothing merging. The sweep is
the only thing that is red, and it is red on `main` rather than on the
PR, so looking at the pull request tells you nothing is wrong. It also
takes the RECONCILER down with it — the part that re-dispatches cd.yml
when main's tip and the last successful deploy differ — so merges made
before the rename would not have shipped either.
Fixed by naming the current owner. This is the only load-bearing
reference in .github (`git grep maonakamoto origin/main -- .github` finds
this line and the comment above it, nothing else).
Renames like this cannot be caught by CI in the repo that breaks: the
workflow that would run the check is the workflow that fails to load.
Worth a fleet sweep for `uses: maonakamoto/` in every repo, since one
account rename breaks every repo that calls a shared workflow, all at
once and all silently.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nothing has merged or deployed in this repo since the GitHub account was renamed
maonakamoto→catomean. Every auto-merge run since fails before it starts:No log, no step, nothing to read.
Cause
GitHub redirects a renamed owner for the REST API and for git remotes —
gh api repos/maonakamoto/dotfilesstill answerscatomean/dotfiles, which is exactly what makes this hard to see — but the Actions resolver does not follow the redirect when loading a reusable workflow. It looks for an owner that no longer exists and fails the whole run before any step exists.Why it was invisible
This is the failure mode
auto-merge.yml's own header warns about, arriving from the other direction:mergeStateStatus: CLEAN,mergeable: MERGEABLE, every check passing.main, not on the PR. Looking at the pull request tells you nothing is wrong — it just sits there looking ready.It also takes the reconciler down with it — the part of the sweep that re-dispatches
cd.ymlwhen main's tip and the last successful deploy differ — so any merge that landed before the rename would not have shipped either.Fix
Name the current owner. This is the only load-bearing reference in
.github:Note for the fleet
A rename like this cannot be caught by CI in the repo it breaks — the workflow that would run the check is the workflow that fails to load. One account rename breaks every repo calling a shared workflow, all at once and all silently. Worth sweeping
uses: maonakamoto/across every repo.Verified
catomean/dotfilesexists, default branchmaster, and still contains.github/workflows/auto-merge-sweep.yml.🤖 Generated with Claude Code