fix: move uniq-by-line field from output to issues #5253
Merged
Conversation
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
ldez
added
area: config
bombsimon
approved these changes
Dec 25, 2024
ldez
force-pushed
the
fix/move-uniq-by-line
branch
from
5f1446c to
c41b849
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR deprecated the old
output.uniq-by-line, and replaced it withissues.uniq-by-line.This option has a meaning close to
max-issues-per-linterandmax-same-issues.The flag
--uniq-by-lineis not impacted, it's only about the file configuration.The old
output.uniq-by-linestill works but with a deprecation log message.