G3-5: URGENT target=hotfix/urgent, repo now owns branches (include=[bugfix/**] only, no exclude key) - expect EXCLUDE via include.branches (not org settings) - #57
Open
alan-hacktron wants to merge 1 commit into
Conversation
Hacktron Security Check - SkippedReason: Hacktron skipped this scan because the target branch |
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.
Same target branch and same EXCLUDE verdict as G3-1, but the mechanism has flipped: repo now owns the branches dimension (include.branches=[bugfix/**], no exclude.branches key at all), so org's scan_exclude_branches=[hotfix/*] no longer applies. hotfix/urgent simply doesn't match the repo's own include pattern. Expected: EXCLUDE, but reason should now say "does not match include.branches in .hacktron/config.yaml", not "your organization's settings" — same verdict as G3-1, different reasoning path.