Skip to content

docs(merge-queue): document improved required status check picker#236

Open
samgutentag wants to merge 2 commits into
mainfrom
sam-gutentag/merge-queue-required-status-picker
Open

docs(merge-queue): document improved required status check picker#236
samgutentag wants to merge 2 commits into
mainfrom
sam-gutentag/merge-queue-required-status-picker

Conversation

@samgutentag

@samgutentag samgutentag commented Jun 11, 2026

Copy link
Copy Markdown
Member

Summary

Documents two improvements to the Required Status Checks picker in Merge Queue Settings (trunk2 #4152):

  1. The picker now draws from GitHub status check contexts and check run names recorded on recent PRs (more accurate and reliable data).
  2. Freeform text input is now supported when a check name is not yet in the list.

Changes:

  • New changelog entry: changelog/2026-06-11-merge-queue-required-status-picker.mdx
  • Updated step 3 in the "Configure in the Trunk UI" section of merge-queue/administration/advanced-settings.mdx to describe both the populated list and freeform input
  • docs.json nav updated to include the changelog entry in June 2026

Source

Test plan

  • Check Mintlify preview link (posted on the PR by the Mintlify GitHub app)

Generated by Claude Code

@claude
docs(merge-queue): document improved required status check picker
f244d47 
The picker in Merge Queue Settings now draws from GitHub status check and
check run tables (trunk2 #4152), and supports freeform input when a check
name is not yet in the list.

Co-Authored-By: Claude <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview Jun 11, 2026, 12:16 PM

@samgutentag samgutentag marked this pull request as ready for review June 11, 2026 12:13
@samgutentag samgutentag added the ready to merge Verify docs PR: customers can use this. Ready to publish. label Jun 11, 2026 — with Claude
@samgutentag Claude

samgutentag commented Jun 11, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 11, 2026): live

Verified: customers can use this. Ready to publish.

  • Eng PR: trunk-io/trunk2#4152
  • Flag: none (no feature flag detected in PR diff or body)
  • Flag state: no gate; feature shipped directly on merge
  • Signals:
    • Eng PR #4152 merged 2026-06-11 by trunk-staging-io[bot]
    • No useFlag, useFeatureFlag, or LaunchDarkly references in the changed files
    • All eng PRs merged, no flag = live

Approve and merge when docs review is complete.

Generated by Claude Code

blx
blx reviewed Jun 11, 2026
View reviewed changes
Comment thread changelog/2026-06-11-merge-queue-required-status-picker.mdx Outdated
Comment on lines +9 to +15
**The required status check picker in Merge Queue Settings now shows actual CI job names observed on your pull requests.**

When configuring required status checks in **Merge Queue Settings**, the picker now populates from GitHub status checks and check runs recorded on your repository's recent pull requests. This gives you accurate, up-to-date check names to select from instead of a manually maintained list.

Two improvements shipped together:

- **Real check names.** The picker pulls from GitHub status check contexts and check run names, so the names you see match exactly what GitHub reports.

@blx blx Jun 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It showed real names before too - selecting statuses from the Settings page was never a manual list - it's just that the earlier system that observed them from Github jobs was no longer running. This resolves that. The freeform input is new though

@samgutentag samgutentag Jun 11, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch — you're right, the picker always observed real names (the prior wording even said "seen on recent PRs"); the earlier observation pipeline had stopped and this restores it. Since the only genuinely new bit is the freeform input, I'm dropping the standalone changelog entry and keeping this as a docs update. The Required Status Checks steps now describe the observed-names behavior plus the new type-to-add input, without the inaccurate "manual list → real names" framing.

@samgutentag @claude
docs(merge-queue): drop changelog entry, keep as doc-only update
b347252 
Per blx review: the picker always observed real check names (it was never a
manual list); the prior observer had stopped and this restores it. The only
genuinely new bit is freeform input. Small fix + minor addition -> documented
on Advanced Settings, not a standalone changelog entry.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@samgutentag samgutentag added the changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). label Jun 12, 2026 — with Claude
@samgutentag Claude

samgutentag commented Jun 12, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 12, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: LaunchDarkly not consulted (no feature flag found)
  • Eng PR links: trunk-io/trunk2#4152
  • Flag: none
  • Signals checked: eng PR merged per prior sweep; no LD flag detected
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep · June 12, 2026

Generated by Claude Code

@samgutentag Claude

samgutentag commented Jun 13, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 13, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: LaunchDarkly not consulted (no feature flag identified; documents existing product behavior)
  • Eng PR links: none (documents existing behavior)
  • Flag: none
  • Signals checked: prior sweep chain (consistent live verdict); no regression signals June 13, 2026
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep · June 13, 2026

Generated by Claude Code

@samgutentag Claude

samgutentag commented Jun 14, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 14, 2026): live

Feature confirmed live in production. No regression signals detected. Ready to merge.

  • Flag state: N/A - no LaunchDarkly flag identified
  • Eng PR: none referenced
  • Linear: none
  • Signals checked: prior sweep chain (consistent live), no regression signals today
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep - June 14, 2026

Generated by Claude Code

@samgutentag Claude

samgutentag commented Jun 15, 2026

Copy link
Copy Markdown
Member Author

Verification status (June 15, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: none - no LaunchDarkly flag identified
  • Eng PR: trunk-io/trunk2#4152 (trunk-io/trunk2 access unavailable this session; live verdict carried forward from June 14, 2026)
  • Flag: none
  • Signals checked: trunk-io/trunk2 inaccessible in this session; prior sweep confirmed live June 14, 2026; no LD flag to check
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep - June 15, 2026

Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@blx blx blx left review comments

Assignees

No one assigned

Labels

changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). ready to merge Verify docs PR: customers can use this. Ready to publish.

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@samgutentag @blx @claude