Enable triagebot's merge conflict notifications #14508
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rustbot
added
the
S-waiting-on-review
|
Oh great, I had written my own script to check for my PR mergeability and send a notice via Telegram, but having it through triagebot is much better! |
|
Oh nice, thanks! |
|
Well… it works, as a simple merge which fixes the Clippy version for a lint triggered a mass check… and ~80 PRs were flagged by triagebot as non-mergeable and got a message! |
|
That explains my 80+ Clippy notifications |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we migrated away from bors I've missed this feature, fortunately triagebot supports it too - https://forge.rust-lang.org/triagebot/merge-conflicts.html
r? @flip1995
changelog: none