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.

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

Support user owner #5

Open
mr-linch opened this issue May 20, 2021 · 4 comments · May be fixed by #168
Open

Support user owner #5

mr-linch opened this issue May 20, 2021 · 4 comments · May be fixed by #168
Milestone

Comments

@mr-linch
Copy link
Member

mr-linch commented May 20, 2021

At now only organization packages is supported, we need to add user packages support.

@mr-linch mr-linch added this to the 1.1.0 milestone May 20, 2021
@kinoute
Copy link

kinoute commented Oct 8, 2021

Any news on this? Support for owner and untagged images would be nice!

@vlussenburg
Copy link
Collaborator

@kinoute Untagged images was released in v1.1.0.

@lazyfrosch lazyfrosch linked a pull request Mar 26, 2023 that will close this issue
@lazyfrosch
Copy link

See #168 for an implementation.

You should be able to test using:

  delete-untagged-images:
    permissions:
      packages: write

    name: Delete Untagged Images
    runs-on: ubuntu-latest
    steps:
      - uses: lazyfrosch/ghcr-delete-image-action@main
        # uses: bots-house/ghcr-delete-image-action@v1.1.0
        with:
          owner: some-username
          name: some-package
          is_user: true
          token: ${{ secrets.GITHUB_TOKEN }}
          untagged-keep-latest: 3

@rohanmars
Copy link

I fixed this in a new project. https://github.com/dataaxiom/ghcr-cleanup-action. However, to implement this you can lookup the repository from the octokit api and test if it's an organization or a user project type. So you don't have to hard code it in the action setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants