Skip to content

Document required status checks configuration in Trunk UI#461

Merged
trunk-staging-io[bot] merged 1 commit intomainfrom
sam-gutentag/required-statuses-ui
Mar 16, 2026
Merged

Document required status checks configuration in Trunk UI#461
trunk-staging-io[bot] merged 1 commit intomainfrom
sam-gutentag/required-statuses-ui

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Add docs for configuring required CI status checks directly from the Trunk Merge Queue settings UI. New section in advanced settings with resolution priority table, and a note in the getting started guide.

@trunk-staging-io
Copy link
Copy Markdown

trunk-staging-io bot commented Mar 12, 2026

😎 Merged successfully - details.

Added Required Status Checks section to advanced-settings.md with
CI job selector configuration. Added cross-reference hint to
configure-ci-status-checks.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@samgutentag samgutentag force-pushed the sam-gutentag/required-statuses-ui branch from d2d3a42 to bc80d7e Compare March 16, 2026 21:53
@claude
Copy link
Copy Markdown
Contributor

claude bot commented Mar 16, 2026

Claude finished @samgutentag's task in 1m 1s —— View job


PR Review

  • Read changed files
  • Check repo guidelines
  • Review for typos, grammar, and formatting
  • Provide feedback

The documentation changes are well-written and clear. A few minor observations:

merge-queue/administration/advanced-settings.md

  • The new "Required Status Checks" section is well-structured and consistent with the surrounding sections.
  • Minor: Step 3 in the "How to configure" list contains two sentences while steps 1, 2, and 4 are single phrases. Consider splitting or merging: "Use the CI job selector to choose which status checks must pass (the selector shows CI jobs seen on recent PRs)."
  • Minor: The PR description references a "resolution priority table" but no table appears in the diff — the description may be outdated/inaccurate relative to the final changes. Not a blocker, but worth aligning.
  • The {% hint %} block at the end summarizes what the intro paragraph already states. It's slightly redundant, but acceptable as a callout for readers who skim.

merge-queue/getting-started/configure-ci-status-checks.md

  • The cross-reference hint is clean and helpful.
  • The anchor #required-status-checks correctly matches the new section heading ## Required Status Checks. ✓

No blocking issues found. The content is accurate, the cross-references are correct, and the writing is clear.

@github-actions
Copy link
Copy Markdown

/trunk merge

Copy link
Copy Markdown

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Auto-approved: Claude code review passed.

@trunk-staging-io trunk-staging-io bot merged commit 42ddc23 into main Mar 16, 2026
3 of 6 checks passed
@trunk-staging-io trunk-staging-io bot deleted the sam-gutentag/required-statuses-ui branch March 16, 2026 21:55
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