Normalise inputs names #56
Labels
Milestone
Comments
Merged
vlaurin
added a commit
that referenced
this issue
Jan 7, 2023
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`.
vlaurin
added a commit
that referenced
this issue
Jan 7, 2023
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`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Inputs related to inclusion or exclusion of versions should be normalised to follow the naming convention:
prune-prefix: include versions for pruningkeep-prefix: exclude versions from pruningThis builds on the pattern initially used by
keep-lastand later bykeep-tagsandkeep-tags-regexesand will help streamline adoption/usage by offering a new way of documenting usage.If possible, all
keep-inputs should always take precedence over theprune-inputs as this is the less destructive approach (ie. better to prune less than too much).Backward compatibility
Existing inputs affected by this which do not currently follow the convention (
older-than,untaggedandtag-regex) will be flagged as deprecated and preserved for the foreseeable future (as a minimum until v1.0.0, possibly more) so as to offer a transition period for consumers.The text was updated successfully, but these errors were encountered: