Skip to content

docs(merge-queue): note Forced badge for force-merged PRs in queue dashboard#578

Draft
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/mq-forced-badge-in-pr-list
Draft

docs(merge-queue): note Forced badge for force-merged PRs in queue dashboard#578
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/mq-forced-badge-in-pr-list

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Summary

  • Adds a "Visibility in the queue dashboard" section to force-merge.md noting that force-merged PRs now display a Forced badge in the merge queue PR list

Related

  • trunk-io/trunk2#3708 (shipped in v161)

Test plan

  • Verify the new section renders correctly on docs.trunk.io

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com


Generated by Claude Code

…shboard

Force-merged PRs now show a "Forced" badge in the merge queue PR list
(trunk-io/trunk2#3708, shipped in v161).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@trunk-staging-io
Copy link
Copy Markdown

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
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 25, 2026

Claude finished @samgutentag's task in 33s —— View job


PR Review: docs(merge-queue): note Forced badge for force-merged PRs

  • Gather context and read changed files
  • Review for typos, grammar, and formatting issues
  • Review for documentation best practices
  • Post final review

The added section (merge-queue/using-the-queue/force-merge.md, lines 87–89) looks good overall. No typos or grammatical issues. A minor observation:

Minor (non-blocking): Terminology inconsistency

The section heading uses "queue dashboard" while the body uses "merge queue PR list" — these refer to the same UI surface but with different names.

### Visibility in the queue dashboard
Force-merged pull requests appear with a **Forced** badge in the merge queue PR list.

Consider aligning them — either both "queue dashboard" or both "merge queue PR list". For example:

Force-merged pull requests appear with a Forced badge in the queue dashboard PR list.

Or update the heading to match the body:

Visibility in the merge queue PR list

This is a minor style nit and does not block the PR.


Summary: The section is concise, well-placed (before "Next steps"), and correctly formatted with ### heading and **Forced** bold for the UI badge — consistent with the rest of the document. No blocking issues.

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Auto-approved: Claude code review passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants