-
Notifications
You must be signed in to change notification settings - Fork 1
Add --block-on to select which blocking rules gate a CI scan #149
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
8cdc94e
Add --block-on to select which blocking rules gate a CI scan
Ibrahimrahhal 0fef2c1
Merge origin/main into ci-blocking-rules
Ibrahimrahhal c8f6ddb
Aggregate every page of blocking issues before reporting the gate fai…
Ibrahimrahhal 3988e44
Use direct rule-slug examples instead of double negatives
Ibrahimrahhal 60a4a2a
Bump version to 1.10.0 for the --block-on flag
Ibrahimrahhal 72f683b
Report the blocked-issue count from the server total, not extra page …
Ibrahimrahhal 9d4ecc2
Drain the request body in the test HTTP stub before answering
Ibrahimrahhal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
[P2] Generate requested artifacts before exiting the gate
A blocking response exits here, but report generation starts at line 364 and SBOM generation at line 458. As a result, the newly documented command
corgea scan --block-on no-criticals --out-format sarif --out-file results.sarifnever writesresults.sarifwhen the rule actually trips;--sbomis skipped too. Those failing CI runs are exactly where the diagnostic artifacts are needed, and--fail-onalready avoids this by evaluating its exit after artifact generation. Store the blocking result, generate requested outputs, then exit 1 (while still failing immediately on API/configuration errors), and add a stubbed CLI test combining a blocking response with--out-fileor--sbom.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.
I agree with this finding and think it should be addressed.
high: Generate requested artifacts before exiting the gate
The blocking branch exits before report and SBOM generation later in the function. Consequently, the newly documented combination of --block-on with SARIF produces no SARIF precisely when the gate detects violations. Preserve the blocking result, generate requested artifacts, and exit afterward; API and configuration errors can still fail immediately.
Proof or reproduction: