Normalize report-format instructions for security scan workflows - #48013
Merged
pelikhan merged 2 commits intoJul 25, 2026
Conversation
4 tasks
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix report formatting issues for non-compliant workflows
Normalize report-format instructions for security scan workflows
Jul 25, 2026
pelikhan
marked this pull request as ready for review
July 25, 2026 14:20
pelikhan
deleted the
copilot/workflow-style-normalize-report-formatting-f7869902-4a63-492f-9d61-0ea22c2b5b21
branch
July 25, 2026 14:21
Contributor
There was a problem hiding this comment.
Pull request overview
Updates security scan reporting prompts to enforce consistent heading hierarchy and progressive disclosure.
Changes:
- Adds
###/####heading guidance. - Requires visible summaries and collapsible finding details.
- Synchronizes generated workflow hashes.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/daily-squid-image-scan.md |
Adds report-format requirements. |
.github/workflows/daily-squid-image-scan.lock.yml |
Updates generated body hash. |
.github/workflows/daily-vulnhunter-scan.md |
Adds report-format guidance; summary-section requirement needs clarification. |
.github/workflows/daily-vulnhunter-scan.lock.yml |
Updates generated body hash. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 4/4 changed files
- Comments generated: 1
- Review effort level: Medium
Comment on lines
+122
to
+124
| Structure the issue body with `###` and `####` headings only. Keep the summary | ||
| and highest-confidence findings visible, and wrap supporting evidence or | ||
| per-finding deep dives in `<details><summary>...</summary>` blocks. |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
Two scheduled reporting workflows were still missing explicit markdown style guidance for section hierarchy and progressive disclosure. This aligns their prompt instructions with the repo’s reporting conventions so generated issue bodies are easier to scan and less likely to regress.
Scope
.github/workflows/daily-squid-image-scan.md.github/workflows/daily-vulnhunter-scan.mdPrompt format requirements
###/####section headings only<details><summary>...</summary>blocksWorkflow artifact sync
.lock.ymlfiles so generated workflow artifacts match the updated prompt bodiesExample of the added guidance