Normalize progressive-disclosure guidance across reporting workflows#44960
Merged
pelikhan merged 2 commits intoJul 11, 2026
Merged
Conversation
4 tasks
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Normalize report formatting for non-compliant workflows
Normalize progressive-disclosure guidance across reporting workflows
Jul 11, 2026
pelikhan
approved these changes
Jul 11, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Standardizes progressive-disclosure guidance across six reporting workflows and synchronizes generated workflow metadata.
Changes:
- Adds consistent report-structure guidance and examples.
- Aligns summaries and collapsible detail labels.
- Regenerates paired lock-file hashes.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/org-health-report.md |
Adds report-format example. |
.github/workflows/org-health-report.lock.yml |
Updates compiled metadata. |
.github/workflows/daily-security-observability.md |
Adds disclosure guidance. |
.github/workflows/daily-security-observability.lock.yml |
Updates compiled metadata. |
.github/workflows/daily-model-inventory.md |
Adds report-format example. |
.github/workflows/daily-model-inventory.lock.yml |
Updates compiled metadata. |
.github/workflows/daily-malicious-code-scan.md |
Adds summary-format guidance. |
.github/workflows/daily-malicious-code-scan.lock.yml |
Updates compiled metadata. |
.github/workflows/daily-issues-report.md |
Updates report template and details label. |
.github/workflows/daily-issues-report.lock.yml |
Updates compiled metadata. |
.github/workflows/daily-code-metrics.md |
Aligns both report variants. |
.github/workflows/daily-code-metrics.lock.yml |
Updates compiled metadata. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 12/12 changed files
- Comments generated: 4
- Review effort level: Medium
| Structure reports as: overview → key metrics/issues → collapsible detail → next actions. No newline at end of file | ||
| **Report Structure Guidelines** | ||
|
|
||
| - Use `###` (or lower) headers only. |
Comment on lines
247
to
+248
| <details> | ||
| <summary>📈 Detailed Metrics</summary> | ||
| <summary><b>View Full Details</b></summary> |
Comment on lines
+516
to
+521
| **Report Structure Guidelines** | ||
|
|
||
| - Use `###` (or lower) headers only. | ||
| - Keep summary and critical actions visible; move long detail into `<details>` blocks. | ||
| - Structure reports as: overview → key metrics/issues → collapsible detail → next actions. | ||
|
|
Comment on lines
+278
to
+280
| - Use `###` (or lower) headers only. | ||
| - Keep summary and critical actions visible; move long detail into `<details>` blocks. | ||
| - Structure reports as: overview → key metrics/issues → collapsible detail → next actions. |
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.
Six report-producing workflows were missing the standard progressive-disclosure guidance used elsewhere in the repository, which made their output format less consistent and less scannable. This change aligns those workflows on the shared report structure pattern: visible summary first, verbose detail behind
<details>.Scope
daily-issues-reportdaily-code-metricsdaily-security-observabilityorg-health-reportdaily-model-inventorydaily-malicious-code-scanPrompt normalization
###or lower headers<details>Output template alignment
Compiled workflow sync
.lock.ymlfiles so the compiled workflow definitions remain in sync with the markdown sources.