G4-E7: exclude.keywords has 51 entries - IMPORTANT: this specifically tests whether the PR #692 max-cap fix is deployed yet - #64
Open
alan-hacktron wants to merge 1 commit into
Open
Conversation
Hacktron config could not be readHacktron is scanning this PR using your organization's default settings instead. |
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.
Before PR #692, exclude/include keywords/labels/authors had no
.max()at all — this array would have parsed as VALID under the old schema. After #692, it's capped at MAX_SCAN_FILTER_ITEMS=50, so this 51-entry array should fail validation and invalidate the whole config, same as E1-E6.This PR is a deployment probe, not just a correctness test:
Check which one actually happens before assuming the fix is live in whatever environment scans this repo.