Skip to content

[TRUNK-17692] Document GitHub status posting for merge queue PRs#457

Open
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/github-merge-queue-statuses
Open

[TRUNK-17692] Document GitHub status posting for merge queue PRs#457
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/github-merge-queue-statuses

Conversation

@samgutentag
Copy link
Member

Summary

• Added new "GitHub status posting" section to Advanced Settings with toggle description, status table, and use cases
• Updated Monitor queue status to mention commit statuses as a way to track queue state from GitHub

Context links

  • trunk-io/trunk2#2585 (merged 2026-01-26)

Files changed

  • merge-queue/administration/advanced-settings.md — new "GitHub status posting" section
  • merge-queue/using-the-queue/monitor-queue-status.md — added bullet about commit statuses

Open questions

  1. What is the exact status check name? (trunk/merge-queue assumed from context)
  2. Are the status descriptions exactly as listed (Waiting in queue, Testing, Merging, etc.) or different?
  3. Does the status persist after the PR is merged/removed from queue?

Test plan

  • Check GitBook preview for both pages
  • Verify the status table renders correctly
  • Confirm cross-link to advanced settings works

🤖 Generated with Claude Code

Add docs for the GitHub commit status feature that posts queue position
and state on PRs. New section in advanced settings and a mention in the
monitor queue status page.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@trunk-staging-io
Copy link

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

@samgutentag samgutentag changed the title Document GitHub status posting for merge queue PRs [TRUNK-17692] Document GitHub status posting for merge queue PRs Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant