Support reusable paths blocks via yaml anchors #13
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
Default value is fine: opened, synchronize, reopened
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.
YAML already supports anchors as a way to avoid copy-pasting repeated parts of the document.
This could be used to embed some rule (i.e. list of paths expressions) into another rule.
It's a more ergonomic alternative to checking several rules with
||operator inside workflowifstatement.YAML anchors however doesn't allow merging of lists.
If we use anchor to embed another rule, we actually get a nested list.
This PR implements flattening of the rule paths expressions, which enables usage of anchros.
Fixes #12