Consolitate matrix configuration #941
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
|
I could have waited for a review but I don't want to waste time and test this with tomorrow's build. |
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.
I've created an action that lets us re-use a dynamic matrix configuration for both, building on copr and running checks.
The matrix from both touched workflows were simply merged and there is still some deduplication work ahead. But at least they share a common place now and one can ask for a matrix using workflow_dispatch events now.
Also, some of the low-hanging-fruit optimizations like
inputs.strategy == matrix.nameremoval incheck-snapshots.ymlare not done to keep this PR reviewable.