Define “success” as a single CI task, refactor Bors & release config #237
Conversation
This file contains 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
|
OK, I think Cirrus does not like me telling it to run an empty image 😹 |
|
rebased to fix merge conflict, boops @duckinator. |
|
bors r+ |
bors bot
added a commit
that referenced
this pull request
Jan 3, 2021
237: Define “success” as a single CI task, refactor Bors & release config r=duckinator a=nbraud - [x] Introduced aliases for each task group - [x] Introduced a “CI success” task that depends on all relevant tasks - [x] Refactored the Bors config and release task to depend on that task Closes #236 Co-authored-by: nicoo <nicoo@mur.at>
|
Build failed:
|
|
WTF? |
|
Build succeeded:
|
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.
Closes #236