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

[samgutentag]

Adds documentation for the Label Commands feature (trunk2 PR #3956, shipped in v175).

Changes

• Documents label-based enqueue/cancel as a submission method in the reference page
• Adds a Label Commands section covering how to enable the feature, configure the enqueueing label, and how apply/remove works

Context

• trunk2 PR: https://github.com/trunk-io/trunk2/pull/3956
• Linear: TRUNK-18126
• Docs requested by Phil in PR description
• Note: Replaces the stale sam-gutentag/mq-configurable-enqueue-label branch (PR [feature not live] docs(merge-queue): document configurable label commands for enqueueing #659) which had conflicting changes from before main was updated. This branch starts from current main with only the reference.md change.

---

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 41s —— View job

---

Review summary

• Read the changed file
• Review the diff
• Check related context (heading conventions in reference.md, terminology in advanced-settings.md, "enqueueing" spelling across merge-queue/)
• Post inline comments for issues
• Post final review summary

Result: non-blocking. The new content is clear, accurate, and well-placed. I left 4 inline comments — all polish, none required to ship.

Findings

1. Heading case (line 43–47) — ## Label Commands / ### Enabling Label Commands use Title Case, but every other heading in reference.md is sentence case (## Custom merge commit titles, ### How it works, ### Example). The neighboring advanced-settings.md is mixed, so this is a file-local consistency point, not a repo-wide one.
2. "Label Commands" vs "label commands" — the term flips between Title Case (header, lines 45/49/51, link text on line 23) and lowercase (prose on lines 23 and 41). Pick one. If you take the heading suggestion above, lowercase everything; otherwise normalize the prose to Title Case.
3. Missing parallel cross-reference (line 41) — line 23 links to the new section, the matching cancellation bullet doesn't. Easy parallelism win.
4. Vague configuration location (line 51) — "you can configure the enqueueing label name" doesn't say where. Probably the same panel mentioned one sentence earlier — worth stating explicitly. Bonus: clarify whether renaming the label retroactively affects PRs already carrying the old one.
5. Precondition visibility (line 60) — "The label must already exist… Trunk does not create the label automatically" is a silent-failure trap and currently styled as plain prose, right before an info hint. Consider promoting it to {% hint style="warning" %} so it's not visually outranked by the less-critical note below it.

Things that look good

• Spelling of enqueueing matches existing usage across merge-queue/ (4 prior hits).
• **Merge Queue Settings** matches the heading used in merge-queue/administration/advanced-settings.md:129.
• The new bullets are inserted in the right places (parallel to existing submission/cancellation methods).
• The action/effect table is a nice touch — clearer than prose for two symmetric operations.
• PR title flagging [feature not live] is helpful context for reviewers.

---

Branch: sam-gutentag/mq-configurable-enqueue-label-clean •

[claude]

Heading case inconsistent with rest of file. Every other ## and ### heading in reference.md uses sentence case (## Submitting and cancelling pull requests, ## Custom merge commit titles, ### How it works, ### Example), but the new headings use Title Case. Consider matching the file's existing convention:

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

If you do this, also lowercase "Label Commands" in prose on lines 49 and 51 (and the link text on line 23) so the term is treated consistently as a feature description rather than a proper noun.

Fix this →

[claude]

Missing cross-reference for parallelism with line 23. The submission bullet (line 23) helpfully links to the Label Commands section, but the matching cancellation bullet here doesn't. A reader who lands on the cancellation list first won't know where to learn more. Suggest mirroring the submission bullet:

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]

Vague on where to configure the label name. "You can configure the enqueueing label name" implies a setting somewhere, but doesn't say where. Is it the same Merge Queue Settings > Label Commands location mentioned in the previous sentence, or somewhere else? Consider making it explicit, e.g.:

When enabled, you can set a custom label name in the same panel. The default is trunk-merge-queue-submit.

Also worth confirming whether changing the label name applies retroactively (do PRs already carrying the old label get cancelled? does it require a label to exist beforehand, per line 60?). If there's a known answer, surfacing it here would save a support ticket.

[claude]

Consider promoting to a warning callout for visibility. This is a precondition that, if missed, will silently break the feature — users may assume Trunk creates the label and wonder why nothing happens when they apply it. The next paragraph is already a {% hint style="info" %}, so the contrast in style suggests this line is less important than it actually is. Suggest:

Suggested change

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

[github-actions]

Auto-approved: Claude code review passed.