Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qlty check --all --fix #1197

Merged
merged 2 commits into from
Nov 21, 2024
Merged

qlty check --all --fix #1197

merged 2 commits into from
Nov 21, 2024

Conversation

lsegal
Copy link
Member

@lsegal lsegal commented Nov 21, 2024

No description provided.

Copy link
Contributor

qltysh bot commented Nov 21, 2024

❌ 2 blocking issues (2 total)

Tool Category Rule Count
qlty Duplication Found 32 lines of similar code in 2 locations (mass = 181) 2

qlty successfully analyzed this pull request in 4m.

Copy link
Member

@brynary brynary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lsegal hah, nice.

I am curious how the linters did... Is this PR the literal result of qlty check --all --fix or did you do edits?

From my demo at lunch today I know that the ESLint provided fixes for unused variables lints are not safe. (And I am not sure if they are recorded as unsafe in the data, which would require the --unsafe option to use them.)

@brynary
Copy link
Member

brynary commented Nov 21, 2024

Oh whoops, I was thinking about the other repo! So I imagine these are mostly Clippy

@lsegal
Copy link
Member Author

lsegal commented Nov 21, 2024

No edits

@lsegal lsegal merged commit 060da81 into main Nov 21, 2024
14 of 15 checks passed
@lsegal lsegal deleted the ls/check-fix branch November 21, 2024 01:28
@brynary
Copy link
Member

brynary commented Nov 21, 2024

Nice!

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

Successfully merging this pull request may close these issues.

2 participants