Skip to content
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

Enable triagebot merge conflict notifications #14972

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Dec 20, 2024

This enables merge conflict notifications on GitHub. Homu was providing this service for us, but it was shut down today. I find these notifications useful, as they give an opportunity for the author to proactively rebase and not require a round trip with the reviewer.

@rustbot
Copy link
Collaborator

rustbot commented Dec 20, 2024

r? @epage

rustbot has assigned @epage.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added A-infrastructure Area: infrastructure around the cargo repo, ci, releases, etc. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 20, 2024
@epage epage enabled auto-merge December 20, 2024 14:46
@ehuss
Copy link
Contributor Author

ehuss commented Dec 20, 2024

Note that after this is merged, the next PR to merge will notify all existing open PRs that currently have merge conflicts, pointing at the wrong PR as the culprit. This is because the conflict notification assumes the PR that just merged is responsible for any conflicts. Hopefully that's not too confusing.

@epage epage added this pull request to the merge queue Dec 20, 2024
Merged via the queue into rust-lang:master with commit 081d7ba Dec 20, 2024
20 checks passed
bors added a commit to rust-lang-ci/rust that referenced this pull request Dec 21, 2024
Update cargo

10 commits in 99dff6d77db779716dda9ca3b29c26addd02c1be..652623b779c88fe44afede28bf7f1c9c07812511
2024-12-18 00:55:17 +0000 to 2024-12-20 15:44:42 +0000
- fix(package): use relpath to cwd for vcs dirtiness report (rust-lang/cargo#14970)
- Enable triagebot merge conflict notifications (rust-lang/cargo#14972)
- fixed the error message for a user to open the crate (rust-lang/cargo#14969)
- fix(package): show dirty filepaths relative to git workdir (rust-lang/cargo#14968)
- Add the `test` cfg as a well known cfg before of compiler change (rust-lang/cargo#14963)
- refactor(cargo-package): let-else to flatten code (rust-lang/cargo#14959)
- fix(cargo-package): add more traces (rust-lang/cargo#14960)
- Do not hash absolute sysroot path into stdlib crates metadata. (rust-lang/cargo#14951)
- docs: add missing argument to Rustup Cargo workaround (rust-lang/cargo#14954)
- fix(cargo-rustc): stabilize higher precedence trailing flags (rust-lang/cargo#14900)
@rustbot rustbot added this to the 1.85.0 milestone Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-infrastructure Area: infrastructure around the cargo repo, ci, releases, etc. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants