The Custom Docker Build Push action is a single action that lives in multiple repositories, as such, updates to the action should be applied to all the repositories that contain the workflow files for this action. Currently, there is no reference to this, so a comment should be added at the top of each file to indicate that updates to one should almost always be propagated to all the rest and link to a list of all the repositories that contain the Custom Docker Build Push action/workflow (this list should probably be maintained in the hubs-docs page about this workflow/action).
Possible Comment
# Updates to this workflow file should be propagated to all the other repositories that implement this action.
# For a list of all repositories that implement this action see: https://github.com/Hubs-Foundation/hubs-docs/blob/master/docs/dev-github-workflows.md
Repositories to update:
The Custom Docker Build Push action is a single action that lives in multiple repositories, as such, updates to the action should be applied to all the repositories that contain the workflow files for this action. Currently, there is no reference to this, so a comment should be added at the top of each file to indicate that updates to one should almost always be propagated to all the rest and link to a list of all the repositories that contain the Custom Docker Build Push action/workflow (this list should probably be maintained in the hubs-docs page about this workflow/action).
Possible Comment
Repositories to update: