Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for multiple regular expressions in prune-tags-regexes #10

Closed
vlaurin opened this issue Feb 17, 2022 · 0 comments · Fixed by #61
Closed

Add support for multiple regular expressions in prune-tags-regexes #10

vlaurin opened this issue Feb 17, 2022 · 0 comments · Fixed by #61
Labels
priority:medium type:feature Feature request
Milestone
0.5.0

Comments

@vlaurin
Copy link
Owner

vlaurin commented Feb 17, 2022 •
edited

For example:

steps:
  - name: Prune
    uses: vlaurin/action-ghcr-prune@main
    with:
      token: ${{ secrets.YOUR_TOKEN }}
      organization: your-org
      container: your-container
      prune-tags-regexes: |
        ^pr-
        ^test-

Given Github actions currently do not natively support YAML lists as input value, multi-value inputs can be achieved using multi-lines, like it's done in Github's own actions/cache.
This is supported by the action toolkit getMultilineInput().
@vlaurin vlaurin changed the title Add support for multiple regular expressions in tag-regex Add support for multiple regular expressions in prune-tags-regexes Feb 26, 2022
@vlaurin vlaurin added this to the 0.5.0 milestone Oct 21, 2022
vlaurin added a commit that referenced this issue Jan 7, 2023
@vlaurin
Normalise filter inputs names
d927303 
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 vlaurin mentioned this issue Jan 7, 2023
Merged
@vlaurin vlaurin closed this as completed in eda6c54 Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:medium type:feature Feature request
Projects
None yet
Milestone
0.5.0
Development

Successfully merging a pull request may close this issue.

Normalise inputs vlaurin/action-ghcr-prune
1 participant
@vlaurin