Skip to content

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
hotfix/urgentfrom
g3-5-src
Open

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
alan-hacktron wants to merge 1 commit into
hotfix/urgentfrom
g3-5-src

Conversation

@alan-hacktron

Copy link
Copy Markdown
Owner

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.

@hacktron-app-stg

Copy link
Copy Markdown

Hacktron Security Check - Skipped

Reason: Hacktron skipped this scan because the target branch hotfix/urgent does not match include.branches in .hacktron/config.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant