Repository navigation
Conversation
KieranP
force-pushed
the
pr-merge
branch
2 times, most recently
from
October 29, 2026 08:07
fab3605 to
968ee9c
Compare
The pull request page already says whether GitHub would merge, so merging sits on its readiness banner: Merge where the card reads ready, Merge When Ready where only required checks running or GitHub working out conflicts hold it back, and Cancel Auto-Merge where auto-merge is on. Merge turns the page into a form opened on GitHub's own default method and its own subject and message for each, read in one gh api graphql call, as no gh pr command prints them. - Merge through gh pr merge, named by the pull request's page and held to the head whose checks the page showed, so a push since fails it - Weigh a form where the list or the checks change, dropping it on a push, a merge or close elsewhere, a lasting blocker or the host off - Say in the form when the repository has auto-merge off or the account may not write to it, and say a failed list read on the page - Click the row's PR or CI glyph to open that page of the panel, in place of a popover that repeated both pages Closes #32 Co-Authored-By: Claude Opus 5.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
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.
The PR page already says whether GitHub would merge a pull request, so merging belongs beside that verdict. Merge turns the page into a form opened on GitHub's own default method and its own subject and message for each, read in one gh api graphql call since no gh pr command prints them. The merge goes through gh pr merge, held to the head whose checks the page showed, so a push since fails it rather than landing unseen commits.
What this does
What I ran
make formatmake lintmake testmake buildWhat I could not verify:
Docs
Docs/design/if this changes a decision, or thereason it does not need one.
unconfirmedif nobody has watched it go either way.