docs(auto-merge): armed --auto may not enqueue; re-issue to enter the merge queue#120
Conversation
… merge queue On a merge-queue repo, the first `gh pr merge --auto` sometimes arms auto-merge (autoMergeRequest set) without enqueuing the PR — checks are green, no unresolved threads, yet mergeQueue.entries is empty and the PR just sits. Re-issuing `gh pr merge --auto` reports "already queued" and the entry then shows AWAITING_CHECKS. Adds a troubleshooting row so this isn't rediscovered as passive waiting. Bump skill 2.15.8 -> 2.15.9. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
documentation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request bumps the version of the GitHub Project skill to 2.15.9 and adds a troubleshooting entry to the auto-merge guide for PRs that are armed but never enter the queue. The reviewer suggested using an active Markdown anchor link instead of a plain-text reference for the mergeQueue.entries GraphQL query to improve navigation and consistency.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
|
From a retrospective on a live multi-PR session.
On a merge-queue repo, the first
gh pr merge NUMBER --autooccasionally arms auto-merge (autoMergeRequestset) without actually enqueuing the PR — all checks green, no unresolved threads, butmergeQueue.entriesis empty and the PR sits indefinitely. Re-issuing the samegh pr merge --autoreports "already queued to merge" and the entry then showsAWAITING_CHECKS.Adds one row to the Merge Queue troubleshooting table so this is fixed by an active nudge +
mergeQueue.entriesverification, rather than rediscovered as passive waiting. Distinct from the existing "enqueue ≠ merged" note (that's about not reporting merged off the exit code; this is about the arm not enqueuing at all).Skill 2.15.8 → 2.15.9. Docs-only.