-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Rustc pull update #20321
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
Rustc pull update #20321
Conversation
Remind to update dev branch while behind too many commits
Rustc pull update
toolchain version does not need to be specified
fix(docs): add newlines between prefix/suffix chapters
Rustc pull update
Rustc pull update
add rdg push git config entry for git protocol pushers
avoid duplicating commands
Rustc pull update
Rustc pull update
Add opaque type attributes
Fix link to GatherBorrows
Rustc pull update
Rustc pull update
use consistent title capitalization
Rustc pull update
Rustc pull update
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: c96a690 Filtered ref: 7b9552d4c39c31aabf6749629da2d4a7e6e1cd60 This merge was created using https://github.com/rust-lang/josh-sync.
|
Hmm, the workflow still didn't run, not sure why. |
|
Workflows do not get triggered by bot commits |
|
I remember having the same issue with releaes-plz on salsa, though I noted down my findings but I can't find the relevant links anymore |
|
Wait, really? Then how are we supposed to merge this? And how can we tell that CI would fail because of a breaking change to |
|
Yea that's the issue, these setups are incompatible with merge queues 🙃 The only proper fix I think is having the bot author the final commit by a non-bot iirc. |
|
Related peter-evans/create-pull-request#48
|
|
CC @Kobzol can you take a look at this (and peter-evans/create-pull-request#48 (comment) in particular)? |
|
Sorryy, I forgot to send a follow-up PR. We can solve this with triagebot. I'll send it when I'm at a PC. |
|
Here it is: #20330 |
|
To unblock this specific PR, just close and reopen it. |
|
Btw I'm not sure why triagebot flagged this PR, it should already be configured properly 🤔 (https://github.com/rust-analyzer/rust-analyzer/blob/ffeb325e09d9b5f2450f10cde8592ef8ffe2b922/triagebot.toml#L20) |
Thanks, I hate it 😀.
It was configured after this PR was filed. |
Yeah, it's not ideal 🙈 For next PRs, triagebot will autoclose/autoopen for you. We're working on switching the CI token to a GitHub app, that should allow running CI automatically without this hack. |
|
Just asking, did you see the workaround of using another token with the |
|
We can use a personal token, which we did historically, but we want to move away from that. GH apps should be the way to go. |
Latest update from rustc.