Skip to content

Don't require exact match on ignored warnings#238

Merged
goneall merged 1 commit intomasterfrom
ignorestart
Dec 2, 2025
Merged

Don't require exact match on ignored warnings#238
goneall merged 1 commit intomasterfrom
ignorestart

Conversation

@goneall
Copy link
Member

@goneall goneall commented Dec 2, 2025

FYI @xsuchy @swinslow - I'm after this merge, the ignored warnings file will ignore any warnings that start with the string in the JSON warnings file rather than requiring a match to the entire string.

This will allow ignoring a class of warnings such as the URL fetches timing out (which happened during my local testing).

@goneall
Copy link
Member Author

goneall commented Dec 2, 2025

Also includes refactoring of the optimized license text matching and updates to the libraries

Signed-off-by: Gary O'Neall <gary@sourceauditor.com>
@goneall goneall merged commit 826a1f8 into master Dec 2, 2025
1 of 2 checks passed
@goneall goneall deleted the ignorestart branch December 2, 2025 23:29
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