Update AGLint to v2.0.10 #187945
Merged
Update AGLint to v2.0.10 #187945
Conversation
This file contains 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
scripthunter7
requested review from
slavaleleka,
a team,
Yuki2718 and
maximtop
Yuki2718
approved these changes
Sep 4, 2024
Alex-302
approved these changes
Sep 4, 2024
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.
This update allows you to ban certain rules based on regex, for more details please refer to https://github.com/AdguardTeam/AGLint?tab=readme-ov-file#no-excluded-rules
Exclude also works for comments. I added an example requested by Yuki in the AGLint issue: AdguardTeam/AGLint#214
If you want to ban some patterns, just edit
.aglintrc.yamlaccordingly.