-
Notifications
You must be signed in to change notification settings - Fork 2k
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
CI: seperate check-labels and check-commits workflows #19120
Conversation
f12b636
to
1e29dd3
Compare
Does bors still need an update? |
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
I don't think so, IIUC "check-commits (pr_check)" should still be reported as before. |
bors merge |
bors cancel |
Canceled. |
bors merge |
Why? |
Build succeeded: |
Optimizing CI queues by letting another ACK'ed PR jump onto the merge train. See Matrix room for the discussion. (Also: The cancel and merge cmd can be in the same message, this makes it more reliable that the canceled PR also is added again before the next merge train is started.) |
And the reasoning as well, simalar to issue/PR closure. I did not see the Matrix message and chat messages get lost easily in the chatter as well. |
Contribution description
They were doing completely seperate things.
Also,
check-commits
was unnecessarily re-run for every label change due to sharedon:
.This'll make it easier to get #19101 in.
Testing procedure
Issues/PRs references