-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Fix cargo dev new_lint for late lint passes #5930
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
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
We could just run cargo dev new_lint --name new_early_pass --pass early
cargo dev new_lint --name new_late_pass --pass late
cargo check somewhere in our CI pipeline I guess? |
Oh good point, I'll look into that. I'm not familiar enough with the pipeline, but I guess that there should also be some cleanup in case more commits are pushed and the workspace is reused. |
I think this can be added here https://github.com/rust-lang/rust-clippy/blob/master/.github/workflows/clippy.yml#L94 Something like that may do:
|
Will try this |
43cd551
to
db6815b
Compare
Testing the failure case... |
db6815b
to
23aada5
Compare
23aada5
to
6dd65b8
Compare
Testing the success case... (Hmm I should have left the previous commit showing the failure for review) |
@matthiaskrgr I think it should be ready to review now :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
@bors r+ |
📌 Commit 6dd65b8 has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Since 30c046e,
LateLintPass
has only one lifetime parameter.I'm not sure how to easily test this, I think adding this kind of tests would be probably part of #5394
changelog: none