Conversation
Extend the lazy-loaded PRMergeState GraphQL query to also fetch: - statusCheckRollup.contexts (individual CI check runs with status/conclusion) - autoMergeRequest (whether auto-merge is enabled, with method) Add server-side handlers for enableAutoMerge/disableAutoMerge mutations using GitHub's enablePullRequestAutoMerge/disablePullRequestAutoMerge GraphQL mutations. Add corresponding message types to ClientToServerMessage and ServerToClientMessage for the new auto-merge operations.
This was referenced Mar 4, 2026
When mergeStateStatus is BLOCKED, derive more specific reasons: - 'Waiting for CI checks to complete' when signalSummary is 'running' - 'CI checks are failing' when signalSummary is 'failed' - 'Waiting for required review approvals' when reviewDecision is REVIEW_REQUIRED - Falls back to generic 'Blocked by branch protection rules' only when no specific reason can be determined Show individual CI check runs (from the lazy-loaded query) in an expandable CIStatusBadge below the merge block reasons, so users can see exactly which checks are pending/failing/passing.
When a PR can't be merged yet (CI running, reviews pending, etc.), show an 'Enable auto-merge' button as an alternative action. This tells GitHub to automatically merge the PR once all branch protection requirements are met. When auto-merge is already enabled (detected via autoMergeRequest from the lazy-loaded merge state query), show a status banner with a 'Disable auto-merge' button. Uses GitHub's enablePullRequestAutoMerge and disablePullRequestAutoMerge GraphQL mutations. Defaults to REBASE merge method to match our existing merge strategy.
Stack navigation pills now show: - Closed PRs: red tint, line-through, circle-slash icon - Draft PRs: dashed border, purple edit icon - CI status: colored bottom border (green=pass, red=failed, amber=running) using signalSummary data already available from the bulk PR query PR info headers (both expanded and compact) now show a state badge for non-open PRs (Merged/Closed/Draft) with appropriate coloring, so the PR state is immediately visible when the review window is open. Added signalSummary to StackNavigationContext entries to support CI status display on pills without additional API calls.
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.
Stack navigation pills now show:
using signalSummary data already available from the bulk PR query
PR info headers (both expanded and compact) now show a state badge
for non-open PRs (Merged/Closed/Draft) with appropriate coloring,
so the PR state is immediately visible when the review window is open.
Added signalSummary to StackNavigationContext entries to support
CI status display on pills without additional API calls.
Stack created with Sapling. Best reviewed with ReviewStack.