@xephon2 Thanks for this suggestion, I think it's a good idea that's worth exploring.

That said, I think this may be better treated as a feature request for the registry itself, rather than as a documentation issue, as the action would need to be developed before it could be documented. For that reason, I'll transfer this issue to the registry repo.

We've been exploring GitHub Actions for our automation needs, but there are a number of moving parts to consider here.

If someone were to develop an action, it would require access tokens to authenticate with the registry and create pull requests, and each plug-in author would need to add the action to their plug-in repositories, as the action would need to fire on pushes to the plug-in repo rather than the registry.

If anyone is interested in picking this up, there is work-in-progress code available in dita-ot/dita-ot#3477, which was designed for a similar purpose and could possibly serve as a template for an action that triggers on pushes to one repo and creates pull requests to another.