Normalise inputs #61
Merged
Normalise inputs #61
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
Resolves #56 Resolves #10 With that change, all filters either start with `keep-` (exclusion) or `prune-` (inclusion). This contributes to making usage of the action more comprehensible and less error prone. Non-normalised inputs are preserved for backward compatibility until v2 and/or a minimum of one year. This change also adds support for multiple regexes via new input `prune-tags-regexes` replacing `tag-regex`.
Inputs are only marked as deprecated and won't be removed until v2.0.0 to offer sufficient migration time.
vlaurin
force-pushed
the
56-normalise-inputs
branch
from
9e2f8b5
to
96bd888
Compare
Leverage normalised filter names to make documentation more straightforward.
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.
Resolves #56
Resolves #10
Inputs are only marked as deprecated and won't be removed until v2.0.0 to offer sufficient migration time.