In particular, this might make it easier to add a standard action to the repository.
By listing it, we can have it searched for, and the user can simply click on configure, and have it created in the intended location and populated based on the template.
This means we can potentially skip the step of searching the reusable workflows repository, allowing other users outside of the organisation to use the CI for testing if they wanted. Also, we can reference the reusable workflows repo and documentation in the template and make it go full circle.
There are probably other small benefits not mentioned here. But definitely a nice to have. Are there any particular downsides to having this that hasn't been mentioned?
Marketplace being the name of where publicly available actions are listed.
Docs: https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace
In particular, this might make it easier to add a standard action to the repository.
By listing it, we can have it searched for, and the user can simply click on configure, and have it created in the intended location and populated based on the template.
An example of this link in action is here:
https://github.com/catalyst/catalyst-moodle-workflows/new/main?filename=.github%2Fworkflows%2Fazure-webapps-node.yml&workflow_template=azure-webapps-node
This means we can potentially skip the step of searching the reusable workflows repository, allowing other users outside of the organisation to use the CI for testing if they wanted. Also, we can reference the reusable workflows repo and documentation in the template and make it go full circle.
There are probably other small benefits not mentioned here. But definitely a nice to have. Are there any particular downsides to having this that hasn't been mentioned?