-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Make sure bors success depends on metadata_collection #9070
Conversation
@bors try |
Make sure bors success depends on metadata_collection r? `@xFrednet` Currently bors runs the `metadata_collection` but merges before the run is finished, because the bors success dummy step didn't depend on it. This also makes sure that the `metadata_collection` test is run at the same time as the other build/test runs to not produce overhead. changelog: none
☀️ Try build successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Woops, nice catch. I'm still learning CI stuff. Thank you!! Sir bors, I formally declare this PR as r+ed |
📌 Commit a131cea has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
How did that work? What happened here? 🤯 |
A magician should never reveal their hand 😂 The trick is that bots ignore HTML comments. If you look at the comment text it included a hidden r+. It was something I thought about on the spot, and find it hilarious. I might adapt that from now on 😂 |
r? @xFrednet
Currently bors runs the
metadata_collection
but merges before the run is finished, because the bors success dummy step didn't depend on it. This also makes sure that themetadata_collection
test is run at the same time as the other base runs to not produce overhead.changelog: none