Skip to content

docs(merge-queue): document Forced badge on force-merged PRs #571

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
samgutentag wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Draft

docs(merge-queue): document Forced badge on force-merged PRs #571

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions merge-queue/using-the-queue/force-merge.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,8 @@ There is no CLI, checkbox, or web app equivalent. This is intentional: Trunk ver
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.
Copy link
Copy Markdown
Contributor

@claude claude Bot Apr 23, 2026

Choose a reason for hiding this comment

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

Minor clarity nit: "it" is slightly ambiguous — it could refer to the PR or to the dashboard entry. Consider making the subject explicit:

Suggested change
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.


### Combining with other flags

Force merge can be combined with other `/trunk merge` flags. The most common combination is with [priority](../optimizations/priority-merging.md) when both urgency and protection bypass are needed — for example:
Expand Down
Loading