From ba76b96cd955ea642a6fdf2e3fd2b5da7f9fee3a Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 23 Apr 2026 10:58:53 +0000 Subject: [PATCH] docs(merge-queue): document Forced badge on force-merged PRs in dashboard 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 --- merge-queue/using-the-queue/force-merge.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/merge-queue/using-the-queue/force-merge.md b/merge-queue/using-the-queue/force-merge.md index dc829ccf..a8fb2ff9 100644 --- a/merge-queue/using-the-queue/force-merge.md +++ b/merge-queue/using-the-queue/force-merge.md @@ -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. + ### 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: