[Bug]: PR detail shows all checks passed without merge-queue state or checks #24991

Before submitting

• I searched existing issues. The open watcher issue [Bug]: watch_pull_request misses merge-queue ejection and leaves the thread watching #20523 concerns missed wakeups; this report concerns the PR detail UI. The earlier queue-badge report Show pull requests as Queued when they enter GitHub's merge queue #12499 is closed as completed.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Summary

The PR detail view can say All checks passed without indicating that GitHub's separate merge-queue checks are still running. The unqualified green summary makes the PR appear finished even while its queue entry is AWAITING_CHECKS.

Steps to reproduce

1. Use a GitHub repository whose protected base branch requires the merge queue.
2. Let every check on the PR head commit pass.
3. Enqueue the PR. While required merge-group workflows are running, open its T3 PR detail view and checks popover.
4. Compare the UI with GitHub's mergeQueueEntry.state and workflow runs for event=merge_group, which have a different commit SHA from the PR head.

Expected behavior

Distinguish passing PR-head checks from the pending merge-queue stage. Show queue membership and pending or failed merge-group checks, or explicitly label the existing summary as PR-head checks and make the separate queue state visible. The exact presentation is a maintainer decision.

Actual behavior

In the live incident, the user reported that T3 showed only All checks have passed, with no queue indication. A contemporaneous GitHub read showed the PR open, queue position 1, state AWAITING_CHECKS, and both Application CI and another required workflow still in_progress on the temporary merge-group commit. Every PR-head check was already green.

The PR then merged while we were inspecting it. Native computer control of T3's detail view confirmed the same unqualified All checks passed summary and the popover listing the head-check population. The view correctly changed to Merged after completion.

Evidence limits: screenshots were captured after the merge, not during AWAITING_CHECKS. The pre-merge UI observation is the user's report; the pre-merge GitHub queue/workflow state was directly queried. This report does not claim a new controlled UI reproduction or that a screenshot captured a pending queue. Private screenshots are not uploaded because they contain unrelated project and thread details.

Source evidence

Public source inspected at 94231a0f716bef1478a325a05518f25f38e8cc22 corroborates the missing distinction:

• PR detail query reads lifecycle, mergeability, autoMergeRequest, and commits(last: 1).statusCheckRollup. It does not request isInMergeQueue, mergeQueueEntry, or the merge-group commit's checks. autoMergeRequest is not queue membership.
• Detail checks summary derives state from detail.checks or the shared summary. Its display passes those checks to the same popover.
• Checks popover renders the check-state label and supplied list without distinguishing head checks from queue checks.
• The same GraphQL file has separate merge-action queries for isMergeQueueEnabled around lines 553 and 566. Supporting queue-aware merge actions does not make queue status available in the detail read above.

This is a focused source inspection, not proof that the installed build exactly matches that upstream commit. No app code was modified.

Impact

Major degradation or frequent failure

Users cannot tell from the PR view why an apparently green PR is still waiting, or that merge-group validation may still fail. It also obscures the separate watcher problem described in #20523.

Version or commit

Installed build revision not established. Public source inspection pinned above; this is not asserted to be the installed revision.

Environment

T3 Code PR detail and checks popover with a GitHub repository using a protected merge queue. Identifying environment and project details omitted.

Logs or stack traces

Sanitized directly observed pre-merge host state:

{
  "pullRequestState": "OPEN",
  "allPrHeadChecksPassing": true,
  "queue": { "position": 1, "state": "AWAITING_CHECKS" },
  "requiredMergeGroupWorkflows": ["in_progress", "in_progress"],
  "mergeGroupCommitDiffersFromPrHead": true
}

Workaround

Inspect queue membership and merge-group workflow runs directly on GitHub. A green PR-head check summary alone does not mean the queue has finished. No branch-protection change or automatic requeue is proposed.

Reported on the user's behalf by GPT 6.1 Sol through the Codex harness in T3 Code. Process IDs, repository/project identifiers, private URLs, paths, PR numbers and thread identifiers from the affected project are omitted.