docs(merge-queue): document starred repos and org grouping in queue selector

[samgutentag]

Summary

Documents new repository selector behavior in the Trunk Merge Queue dashboard, shipped in trunk-io/trunk2#3698:

• Starred repositories pin to the top of the selector list
• Unstarred repositories are grouped by GitHub organization
• Search filters by repository or branch name

Source

• trunk2 PR: https://github.com/trunk-io/trunk2/pull/3698

Test plan

• Preview in GitBook

---

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

---

Review complete

• Gather context
• Read changed file and diff
• Review for typos, grammar, formatting, and documentation best practices
• Post inline comments and final review

---

The new ### Repository selector section is a clean, well-structured addition that follows the existing document's formatting conventions. The content is clear and the placement (after the navigation steps, before Queue overview) makes sense.

Two clarifications flagged with inline comments:

1. Line 29 — Star icon location: "Click the star icon next to the selector" implies the star is outside the dropdown, but typical UI patterns place it next to individual repository names inside the list. If the interaction is actually per-repo inside the dropdown, the description should reflect that. See inline suggestion.

2. Line 33 — Search by branch name: Filtering "by repository or branch name" is mildly confusing in a selector that groups repositories by org — it's not obvious how branch name filtering works or why it's useful here. A brief clarification would prevent reader head-scratching. See inline suggestion.

No typos, grammar issues, or other formatting problems found. Both flagged items are non-blocking clarifications — verify against the actual UI and update if needed.

[claude]

The phrase "next to the selector" suggests the star icon is adjacent to the selector dropdown itself (outside it), but based on typical UI patterns it may actually appear next to individual repository names within the dropdown list. If that's the case, the interaction could be described more precisely:

Suggested change

	**Starred repositories:** Click the star icon next to the selector to star the currently selected repository. Starred repositories always appear at the top of the list, regardless of organization.
	**Starred repositories:** Click the star icon next to a repository in the selector list to star it. Starred repositories always appear at the top of the list, regardless of organization.

If the star icon truly does apply to the "currently selected" repository via a control next to the selector (not inside the dropdown), then the original wording is fine — but it's worth verifying against the actual UI.

[claude]

Since the selector groups repositories (not branches) by organization, filtering "by branch name" may be confusing — it's not obvious why a user would search for a branch here, or what it does (e.g., surfaces repositories whose default branch matches the query?). Consider a brief clarification:

Suggested change

	**Search:** Type to filter the list by repository or branch name.
	**Search:** Type to filter the repository list by name. Search also matches branch names, making it easy to find the right queue when multiple repositories share a branch.

If filtering by branch name has a different meaning (e.g., the queue is per-branch and branches appear as items in the list), it may be worth a short explanation of why both repository and branch names are searchable.

[github-actions]

Auto-approved: Claude code review passed.