fix(workflows): normalize report formatting in output templates#21128
Merged
fix(workflows): normalize report formatting in output templates#21128
Conversation
…ws (#24204) Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
pelikhan
March 15, 2026 22:43
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Normalizes report output templates in a few remaining reporting workflows to match the shared report-formatting guidelines (h3+ headers and progressive disclosure via <details>), reducing inconsistent AI-generated output.
Changes:
- Adjusts a remaining
##header to###in the weekly safe-outputs spec review PR body template. - Wraps the editor status table in
<details>for the weekly editors health check PR body template. - Wraps daily news chart embed sections in
<details>for progressive disclosure.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/weekly-safe-outputs-spec-review.md |
Normalizes “Related Files” header level to h3 within the PR body template. |
.github/workflows/weekly-editors-health-check.md |
Wraps the editor status table in a collapsible <details> block in the example PR body. |
.github/workflows/daily-news.md |
Wraps chart embed sections in <details> blocks under the Trend Analysis section. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
This was referenced Mar 16, 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
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.
Output format templates in several reporting workflows used
##/#headers and lacked<details>progressive disclosure, contradicting the guidelines inshared/reporting.mdand causing inconsistent AI-generated output.Changes
weekly-safe-outputs-spec-review.md— Fixed last remaining## Related Files→### Related Filesinside the PR body code block templatedaily-news.md— Wrapped chart embed sections in<details>for progressive disclosure (was the only reporting workflow with zero<details>tags in its output template)weekly-editors-health-check.md— Wrapped editor status table in<details>in the PR body templateAll other files listed in the issue had already been updated; these three had residual non-compliance.
Before / After (
weekly-editors-health-check.md):