-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix may not to appropriate might not or must not #87445
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
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @kennytm (or someone else) soon. Please see the contribution instructions for more information. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #85874) made this pull request unmergeable. Please resolve the merge conflicts. |
This comment has been minimized.
This comment has been minimized.
b28e9fa
to
ffcf8a0
Compare
@bors r+ |
📌 Commit ffcf8a0 has been approved by |
⌛ Testing commit ffcf8a0 with merge 260af5fb771243a2d36a04c177dc7307f16253c2... |
💔 Test failed - checks-actions |
@kennytm How do I view why it failed? I'm not able to pull up the build logs. |
@bors retry |
☀️ Test successful - checks-actions |
I went through and changed occurrences of
may not
to be more explicit withmight not
andmust not
.