feat(web): pull requests set to merge when ready show GitHub's merge queue icon - #246
Merged
Conversation
…queue icon An open pull request that the host is landing on its own looked like any other open one: the PR state glyph in the sidebar, the command palette, the Pull Requests page rows, the PR tabs and the PR header only knew open, draft, merged and closed. The git status read that feeds the sidebar badge never asked GitHub for the auto-merge flag at all. The GitHub CLI reads now request `autoMergeRequest` alongside the branch's pull request, and the flag travels through the source-control change request and the VCS status contract to the client. The shared badge tone table gains an armed variant that draws GitHub's own merge queue glyph (Primer Octicons, MIT) in amber, and every surface that draws the state glyph reads it: the PR header also arms it from the queue position, since a queued pull request need not carry the standing instruction any more.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
vouch:trusted
badcuban
enabled auto-merge
September 6, 2026 08:31
Main gained a pull request row above the composer and a hover card on pull request links (#244) after this branch forked. Its test fixture built a thread pull request without the new auto-merge field, which failed the typecheck on the merge result. Both new surfaces draw the state glyph from the shared tone table, so they now carry the armed flag as well: the composer row and the hover card read it from the detail once it lands (a queue position counts), and from the thread's own resolution before that. The "armed or queued" rule the PR header used inline is now one helper the three of them share.
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.
An open pull request that GitHub is landing on its own looked like any other open one. The PR state glyph in the sidebar, the command palette, the Pull Requests page rows, the PR tabs and the PR header only knew open, draft, merged and closed, and the git status read that feeds the sidebar badge never asked GitHub for the auto-merge flag.
The GitHub CLI reads now request
autoMergeRequestalongside the branch's pull request, and the flag travels through the source-control change request and the VCS status contract to the client. The shared badge tone table gains an armed variant that draws GitHub's own merge queue glyph (Primer Octicons, MIT) in amber, and every surface that draws the state glyph reads it. The PR header also arms it from the queue position, since a queued pull request need not carry the standing instruction any more.