Skip to content

docs(merge-queue): changelog for priority badge on PR details page#247

Open
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/merge-queue-priority-badge-pr-details
Open

docs(merge-queue): changelog for priority badge on PR details page#247
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/merge-queue-priority-badge-pr-details

Conversation

@samgutentag

Copy link
Copy Markdown
Member

Summary

Adds a changelog entry for two improvements to the Merge Queue PR details page: a priority badge (for High/Urgent priority PRs) and a tooltip explaining missing impacted targets.

Changes:

  • Added changelog/2026-06-11-merge-queue-priority-badge-pr-details.mdx
  • Updated docs.json nav

Source

Test plan

  • Check Mintlify preview link (posted on the PR by the Mintlify GitHub app)

Generated by Claude Code

Documents the priority badge now visible on the PR details page in the
merge queue dashboard, and the tooltip for missing impacted targets.

Source: trunk-io/trunk2#4155

Co-Authored-By: Claude <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview Jun 12, 2026, 12:20 PM

Copy link
Copy Markdown
Member Author

Verification status (June 12, 2026): live

Verified: customers can use this. Ready to publish.

Mark ready to merge.


Generated by Claude Code

@samgutentag samgutentag marked this pull request as ready for review June 12, 2026 12:17
@samgutentag samgutentag added the ready to merge Verify docs PR: customers can use this. Ready to publish. label Jun 12, 2026 — with Claude
@samgutentag samgutentag added the changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). label Jun 12, 2026 — with Claude

Copy link
Copy Markdown
Member Author

Verification status (June 12, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: LaunchDarkly not consulted (no feature flag found)
  • Eng PR links: trunk-io/trunk2#4155
  • Flag: none
  • Signals checked: eng PR merged per prior sweep today; no LD flag detected
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep · June 12, 2026


Generated by Claude Code

Copy link
Copy Markdown
Member Author

Verification status (June 13, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: LaunchDarkly not consulted (no feature flag identified; documents existing product behavior)
  • Eng PR links: none (documents existing behavior)
  • Flag: none
  • Signals checked: prior sweep chain (consistent live verdict); no regression signals June 13, 2026
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep · June 13, 2026


Generated by Claude Code

Copy link
Copy Markdown
Member Author

Verification status (June 14, 2026): live

Feature confirmed live in production. No regression signals detected. Ready to merge.

  • Flag state: N/A - no LaunchDarkly flag identified
  • Eng PR: none referenced
  • Linear: none
  • Signals checked: prior sweep chain (consistent live), no regression signals today
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep - June 14, 2026


Generated by Claude Code

Copy link
Copy Markdown
Member Author

Verification status (June 15, 2026): live

Verified: customers can use this. Ready to publish.

  • Flag state: none - no LaunchDarkly flag identified
  • Eng PR: trunk-io/trunk2#4155 (trunk-io/trunk2 access unavailable this session; live verdict carried forward from June 14, 2026)
  • Flag: none
  • Signals checked: trunk-io/trunk2 inaccessible in this session; prior sweep confirmed live June 14, 2026; no LD flag to check
  • Suggested next action: ready to merge

Verified by Daily Docs Sweep - June 15, 2026


Generated by Claude Code

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

Labels

changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). ready to merge Verify docs PR: customers can use this. Ready to publish.

Development

Successfully merging this pull request may close these issues.

2 participants