Repository navigation
Show when a linked PR is queued to merge - #6
Merged
Merged
Conversation
While a PR waits in GitHub's merge queue, GitHub still reports it as clean and mergeable, so the PR column called it Mergeable. Ask GitHub for isInMergeQueue and label those PRs Queued to merge.
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.
Summary
A PR waiting in GitHub's merge queue now reads Queued to merge in the PR column. While a PR is queued, GitHub still reports it as
CLEANandMERGEABLE, so before this it read Mergeable, the same as a PR nobody has queued.The label is green, like Mergeable, since a queued PR needs nothing from anyone. OVERVIEW.md and README.md now say queued PRs are identified.
Evidence
npm run typecheckpasses,npm testpasses all 335 tests across 12 files, andgit diff --checkis clean.running). Through the daemon, the client bundle includes "Queued to merge", andissues.pull-requestsreturnsisInMergeQueuefrom GitHub for a real issue (falsefor its merged PR). No queued PR was linked to an issue at the time, so there is no screenshot of the label.Merge Danger
Door: two-way
No settings or migrations. Reverting restores the previous query and label.
Blast Radius: small
Only the merge line of open PRs changes. The query asks GitHub for one more field; if GitHub ever rejected it, the PR status lookup would fail with the existing "Could not load PR status" message while issues and workspace actions stay usable.
🤖 Generated with Claude Code