-
Notifications
You must be signed in to change notification settings - Fork 368
Normalize report formatting guidelines across daily workflow prompts #28649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -668,6 +668,8 @@ git diff --name-only | |
|
|
||
| ## Phase 7: Create PR or Report NOOP | ||
|
|
||
| - **Report Formatting**: Use h3 (###) or lower for all headers in your PR body and report content to maintain proper document hierarchy. Wrap long sections in `<details><summary>Section Name</summary>` tags to improve readability and reduce scrolling. | ||
|
||
|
|
||
| ### If files were created: | ||
|
|
||
| Create a pull request with all the new test workflows and Go tests. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this
## Guidelinessection, these guideline lines are plain paragraphs (not a list), and most of them don’t end with Markdown hard line breaks. In CommonMark/GitHub, the new**Report Formatting**line will render in the same paragraph as the preceding guideline (likely concatenating with**Efficiency**), which hurts readability. Consider converting the Guidelines block to a bulleted list (as used in other workflows like.github/workflows/api-consumption-report.md:433-441) or adding consistent hard line breaks so each guideline renders on its own line.