-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Make must_not_suspend
allow-by-default until edge cases are ironed out
#89787
Conversation
r? @nagisa (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
Please add a regression test for the problematic code as reported in the issue. |
Please also make the commit titles/descriptions more meaningful in isolation. Right now they don't contain any context indicating even what is being allowed by default. Copying the PR title to the commit message would help a lot here. While at it, a squash would be good too. r=me once history is rewritten. |
@nagisa my understanding was that bors merge made commit messages disappear, and that people typically review full pr's, not individual commits, is this understanding incorrect? |
Bors merge is a standard
So unless the commits themselves are sufficiently descriptive, it can become quite difficult to scan the history when looking for something relevant.
This really depends on a situation as well as the reviewer. For smaller PRs, reviewing the entire PR as a whole is probably going to be common. When landing a PR requires more cycles of review feedback and fixes, or if the PR is fairly large reviewing commit-by-commit is going to be more common. My concern here is more about the usability of the history once the PR is merged, and less so with the review flow, if that makes sense? |
@nagisa that makes sense, thanks for the thorough answer! I am quite new to git power-user workflows, is the best way to rename all the commits in a branch to use rebase -i with |
|
1429560
to
7b95c7b
Compare
@mati865 I believe the only outstanding review was the commit names! Sorry about the delay, I was away for a few weeks |
I think this PR should be backported to beta 1.57.0 too. Otherwise, after #89826 lands, there'd be no way to turn off the lint on 1.57.0 stable. |
cc @Mark-Simulacrum in case you'd like to review this at the same time as #89826 |
Pulled this PR into #89826, so closing this one. Thanks! |
beta nomination removed as per this comment |
Fixes #89562