Prettify source-build triage comment output format#5602
Merged
Conversation
Restructure the dense stacked **Bold**: lines into labeled sections: a Classification summary table plus Priority, Routing, Cross-references, and Assessment lists, separated by headers and a footer rule. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ellahathaway
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
triageskill's comment template stacked every field as a flat list of**Bold**:lines, which rendered as a dense wall of text that was hard to skim. This restructures it into scannable sections so a maintainer can grok the assessment at a glance.What changed
No behavioral change to the triage logic itself, only the rendered comment layout. All template placeholders and field semantics are preserved.