API to set a package's actions access policy?

[mpint]

Select Topic Area

Question

Body

Hello, I have a template repository that depends on a private Github package in my org.

When the template is used to create a child repository, the Github package fails to install in the newly created repository until the repository is manually added to the package's "Manage Actions access" allowlist on its settings page, which requires intervention every time a child repository is created. It would be nice this could be managed through an API.

Is there any plan to add support for setting a package's actions access policy?

[sabamadadi]

Hello,

While there are some workarounds available now, an official API from GitHub would likely make this process much smoother and fully automated. Opening a feature request is a good step to try to get this on GitHub's roadmap. I would recommend explaining your specific use case and needs to help convince them of the value an API would provide.

Hope this helps!

[tomshabtay]

Hi @sabamadadi,

If possible, can you please share the workarounds you were mentioning?

Thanks!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[mjfpalmer]

I would really love this feature to be added to the REST API, since doing this manually can be painful especially when we have 20+ repos needing access to 60+ packages. That is 1200+ UI operations to perform manually!

[grandmas-favorite]

Hi @mjfpalmer!

I agree that would be a useful addition! Thanks for sharing - you can check our public roadmap to see the kinds of work we are focusing on for the coming year. Smaller fixes won’t be listed, but are often included when work is happening adjacent to it.

As a GitHub user, the most you can do is to share your feedback on this Discussion space with the correct tags (include examples), and trust that we are always working to make GitHub as awesome as possible. We can't guarantee that every bit of feedback sees action, but we are paying attention!

[mjfpalmer]

Thanks @grandmas-favorite. I've worked around this by programatically mimicking the UI's POST that grants repo package access and this has worked, but this is obviously not a long term solution and probably not how you want people hitting your UI.