docs(github-project): verify a PR actually merged through the queue#84
Conversation
…eue' recipe On a merge-queue repo, gh pr merge --merge/--auto only enqueues — the PR stays open and the queue merges later (or stalls). Document that enqueue != merged, the gh-readonly-queue/<base>/pr-<N>-<sha> CI branch naming, and the GraphQL mergeQueue / merge_group / pr-view recipe to confirm the PR actually lands before declaring done. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Pull request overview
Documentation-only addition to the auto-merge guide explaining that on merge-queue repositories, gh pr merge --merge/--auto only enqueues a PR rather than merging it, and providing concrete commands to verify the PR actually landed.
Changes:
- Adds a new "Verifying a PR Actually Merged (enqueue ≠ merged)" subsection to
references/auto-merge-guide.md. - Documents the
gh-readonly-queue/<base>/pr-<N>-<sha>synthetic branch naming used by the merge queue. - Provides GraphQL/
ghrecipes to inspect queue position, watchmerge_groupCI runs, and confirmMERGEDstate.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![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 adds a new section to the auto-merge guide explaining how to verify if a PR has actually merged when a merge queue is in use. The review feedback suggests improving the robustness of the provided gh CLI commands by using GraphQL variables instead of hardcoded placeholders, and utilizing optional chaining in jq expressions to safely handle potentially null fields.
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.
Per the repo's agent-rules: pass values to gh api graphql via -f/-F variables instead of hardcoding owner/name in the query string, and use optional chaining (.mergeQueue?, .mergeCommit?.oid) with a fallback so jq is safe when the merge queue is disabled or the PR is unmerged. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Small addition to
references/auto-merge-guide.md, complementing the existing Merge Queue Behavior section.On a merge-queue repo,
gh pr merge --merge/--autoonly enqueues — the command returns success immediately, the PR stays open, and the queue merges later (or stalls). Reporting "merged" off the exit code is wrong.Adds a "Verifying a PR Actually Merged (enqueue ≠ merged)" subsection: the
gh-readonly-queue/<base>/pr-<N>-<sha>CI branch naming, and the recipe to confirm landing — GraphQLmergeQueue.entriesfor position/state,gh run list --event merge_groupto watch the queue CI, andgh pr view --json state,mergedAtto confirmMERGEDbefore declaring done.Distilled from merging a real PR through a queue where the full-matrix CI ran ~9.5 min on the readonly-queue branch after enqueue.