[feature not live] docs(merge-queue): document configurable label commands for enqueueing

[samgutentag]

Summary

• Documents the new Label Commands setting in Merge Queue Settings
• Explains how to enable label-based enqueue/cancel and configure the label name
• Adds a new "Label Commands" section to the Submit and Cancel PR reference page

Source

• trunk2 PR: https://github.com/trunk-io/trunk2/pull/3956
• Linear: https://linear.app/trunk/issue/TRUNK-18126

Test plan

• Preview in GitBook
• Verify label table renders correctly

---

Generated by Claude Code

[trunk-staging-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

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]

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

---

Claude Code Review

• Read changed files
• Check related docs for style consistency
• Review for typos, grammar, and formatting
• Post inline review feedback

Summary

Reviewed the 27 lines added to merge-queue/using-the-queue/reference.md. Overall the content is clear, well-organized, and follows the existing structure of the page. No typos or grammatical errors found. Posted 4 inline comments covering minor consistency issues:

1. [Line 41] Cancellation bullet should mirror line 23 by linking to the #label-commands anchor.
2. [Lines 72/76] Heading capitalization — rest of the page uses sentence case (Custom merge commit titles, Pull request processing); new headings mix Title Case (Label Commands, Enabling Label Commands) with sentence case (How it works). Recommend sentence case throughout for the page-level style; keep Label Commands capitalized in body prose where it names the UI setting.
3. [Lines 86–87] Adjacent table rows say Merge Queue (row 1) and queue (row 2) — pick one.
4. [Line 89] Nit — the "label must already exist" callout reads as a gotcha and could be a {% hint style="warning" %} to match the existing hint pattern below it.

None of these are blocking; they are all style/consistency suggestions on otherwise-correct content.
· Branch

[claude]

Minor consistency: the parallel bullet on line 23 links readers to the [Label Commands](#label-commands) section, but this bullet only says "(when label commands are enabled)" without the same anchor link. For users skimming the cancellation list, the link is just as useful. Consider mirroring line 23:

Suggested change

	* Removing the configured enqueueing label from a pull request (when label commands are enabled).
	* Removing the configured enqueueing label from a pull request (when label commands are enabled — see [Label Commands](#label-commands) below).

[claude]

Heading capitalization is inconsistent with the rest of the page.

Every other ##/### heading on this page uses sentence case (e.g. ## Submitting and cancelling pull requests, ## Custom merge commit titles, ## Pull request processing, ## Pull request states, ### Example). The new section uses Title Case for ## Label Commands and ### Enabling Label Commands, but then drops back to sentence case for ### How it works — so it's also internally inconsistent.

Recommend sentence case throughout to match the rest of the page:

Suggested change

	## Label Commands
	Label Commands let you enqueue and cancel PRs in the Merge Queue by applying or removing a GitHub label, without leaving a comment or using the CLI.
	### Enabling Label Commands
	## Label commands
	Label Commands let you enqueue and cancel PRs in the Merge Queue by applying or removing a GitHub label, without leaving a comment or using the CLI.
	### Enabling label commands

(You can keep "Label Commands" capitalized in body prose where it refers to the setting name in the UI — the recommendation is just about heading style.)

[claude]

Inconsistent terminology within adjacent rows: the "Submit" row says "Merge Queue" (capitalized) and the "Cancel" row says "queue" (lowercase, no "Merge"). Pick one for both rows.

Suggested change

	| Apply the enqueueing label to a PR | Submits the PR to the Merge Queue |
	| Remove the enqueueing label from a PR | Cancels the PR from the queue |
	| Apply the enqueueing label to a PR | Submits the PR to the Merge Queue |
	| Remove the enqueueing label from a PR | Cancels the PR from the Merge Queue |

[claude]

Nit: This is an important "gotcha" — if the label doesn't exist, nothing happens. It would stand out more (and match the pattern used for the existing info hint below) if wrapped in a warning hint:

{% hint style="warning" %}
The label must already exist in your GitHub repository. Trunk does not create the label automatically.
{% endhint %}

Non-blocking — leaving as a plain paragraph is also fine.

[github-actions]

Auto-approved: Claude code review passed.