Add a ready-to-ship check that depends all jobs #820
Merged
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
mdellweg
force-pushed
the
single_required_workflow_job
branch
from
d809be3 to
a92d3f6
Compare
This is a dummy job that depends on all other test runs, so declaring a single required job in the branch protection rules is sufficient. Also this allows to add and remove scenarios to/from our CI via a pull request. And we can use the same rules for all release branches having different scenarios. [noissue]
mdellweg
force-pushed
the
single_required_workflow_job
branch
from
a92d3f6 to
cdbdbb2
Compare
ggainey
approved these changes
Dec 4, 2023
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.
This is a dummy job that depends on all other test runs, so declaring a single required job in the branch protection rules is sufficient. Also this allows to add and remove scenarios to/from our CI via a pull request. And we can use the same rules for all release branches having different scenarios.
[noissue]