Hi @riker09 ,

Thanks for your feedback!

I have submitted a query for the event ‘registry_package’ doc internally, will update once there’s a response.

FWIW, here’s the link to the documentation: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#registry-package-event-registry_package

And since the internet is a volatile thing, here’s the documentation as the time of writing (sorry for posting it as an image):

Screenshot_2020-02-05 Events that trigger workflows - GitHub Help.png739×483 51.4 KB

PLEASE NOTE: Information gets outdated very quickly, so if you stumble upon this in the future make sure this documentation is still valid.

This is still valid?

Seems that the Github Event Webhhok API was updated and  registry_package was renamed to  package.

https://github.com/octokit/webhooks/releases/tag/v3.0.0

If there has been a rename it has not (yet) made it into the documentation. Here is a screenshot from today (Wed. 26th, Feb. 2020):

Bildschirmfoto von 2020-02-26 11-35-43.png812×492 51.9 KB

Since there is documentation available I guess this topic can be marked as solved. However, I still believe that the feature still needs more attention (like a package name filter) but that is a different story.

[EDIT]

Wait, I already accepted a reply as solution, so nevermind. :slight_smile:

_registry_package _wasn’t working for me. I tried to rename registry_package to package, but I get the following error:

If it wasn’t documented, how exactly people found it to use it?

It was documented at some point, and then it got removed later on. The documentation is updated to the latest changes of GitHub Actions. Sometimes documentation and actual behavior diverge. I would love to see this issue addressed, by having the documentation to be in sync with the released features. It would be helpful to have a documentation changelog as well. And GitHub Actions (Core) should have version tags which then could be referenced in the documentation. I have not spent any research time whatsoever to see if this is an actual feature request somewhere else.

Yeah, I get the same error now. registry_package is not working (anymore?), the workflow does not even show up in the list of workflows of the repository. And renaming the event to package results in the same error “Invalid workflow file”.

I would like to know how to get the package name, so I can use it later in the workflow.