-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: lint ctest-test
crate
#4413
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
df8cafb
to
a9b5944
Compare
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.
Side note, ctest
isn't on the libc-0.2
branch at all so there are no backports needed for these changes.
a9b5944
to
f91bf9c
Compare
3a56cd8
to
9367edd
Compare
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.
LGTM, please squash
9367edd
to
c0cb416
Compare
thx, done. Why isn't libc using the github squash command? |
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.
Thanks!
Annoyingly with merge queues you can't choose the strategy on a case-by-case basis, and we do need to preserve commits in some cases. Sometimes I can squash and force push via the gh UI, but better if the author can do it so they don't get out of sync.
I can use rebase from the UI if something gets stuck on since-fixed tests though, case in point.
run `cargo clippy --all-targets` on `ctest-test`, and fix all default issues. Also added a generic
c0cb416
to
4a88460
Compare
run
cargo clippy --all-targets
onctest-test
, and fix all default issues@rustbot label +stable-nominated