docs(merge-queue): document Forced badge on force-merged PRs#571
docs(merge-queue): document Forced badge on force-merged PRs#571samgutentag wants to merge 1 commit intomainfrom
Conversation
…oard list Force-merged pull requests now show a Forced badge in the Merge Queue dashboard PR list. Adds a one-line callout in the force-merge step-by-step so users know how to identify bypass-protected merges at a glance. Source: trunk2 PR #3708 (merged 2026-04-22) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
|
Claude finished @samgutentag's task in 1m 6s —— View job PR Review
The change is clean — one sentence, properly formatted with surrounding blank lines, no typos, and it adds useful visibility information for users. One minor suggestion (non-blocking): The pronoun "it" on line 50 is slightly ambiguous. I've left an inline suggestion to make the subject explicit. Take it or leave it. Formatting note: The PR description calls this a "callout" but the implementation is a plain paragraph rather than a Review: LGTM — no blocking issues. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| 3. **Merge.** If tests pass, Trunk Sudo merges the PR, bypassing branch protection. Without Trunk Sudo installed and configured, this step will fail. | ||
| 4. **Failure.** If tests fail, the PR is handled like any normal queue failure. See [Handle failed pull requests](handle-failed-pull-requests.md). | ||
|
|
||
| After a PR is force-merged, it shows a **Forced** badge in the Merge Queue dashboard PR list so you can identify which merges bypassed branch protection. |
There was a problem hiding this comment.
Minor clarity nit: "it" is slightly ambiguous — it could refer to the PR or to the dashboard entry. Consider making the subject explicit:
| After a PR is force-merged, it shows a **Forced** badge in the Merge Queue dashboard PR list so you can identify which merges bypassed branch protection. | |
| After a PR is force-merged, the PR shows a **Forced** badge in the Merge Queue dashboard PR list so you can identify which merges bypassed branch protection. |
Not blocking.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
3 participants
Summary
Source
Test plan
Generated by Claude Code