Split SARIF files with multiple runs for GitHub code scanning compliance #11
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.
GitHub's code scanning API now rejects SARIF files containing multiple runs with the same category (effective July 2025). Codacy often generates multi-run SARIF files, causing upload failures.
Changes
Split logic: Added Python script to detect and split multi-run SARIF files into individual files, one run per file. Single-run files pass through unchanged.
Upload strategy:
results.sarifresults-{0..9}.sarifwith unique categories (codacy-run-0, etc.)hashFiles()to skip missing filesError handling: Validates file existence and JSON structure; outputs step variable (
single_run) to control upload flow.Scalability: Supports up to 10 runs; warns if more detected.
Reference: https://github.blog/changelog/2025-07-21-code-scanning-will-stop-combining-multiple-sarif-runs-uploaded-in-the-same-sarif-file/
Original prompt
This pull request was created as a result of the following prompt from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.