Repository navigation
merge: a head already on main is reported, nothing logged - #103
Merged
Merged
Conversation
stacksbot's stale background job ran merge --chore log on a chore-log PR that had merged: it said merged and logged a second merge act for the same sha. merge now fetches main first and stops when the head is already in it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
This was referenced Nov 5, 2026
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
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.
What
merge: after resolving the PR's head, it fetches main. If the head is already on main, it prints<branch> at <sha> is already on main: nothing to merge, nothing loggedand stops. It doesn't land anything or write an act.Why
stacksbot's supervisor saw a stale background job run
merge --chore logon a chore-log PR that had already merged. It reported "merged" and logged a secondmerge-choreact for the same sha (13909e23: a-20261105-034848643 and a-20261105-035351956). I verified both in stacksbot's log.gh pr viewstill returns a merged PR, so nothing stopped it.Authority
This only removes a duplicate record; nothing is authorized differently.
Migration
None.
🤖 Generated with Claude Code