Skip to content

Update comments in Custom Docker Build Push workflow files to indicate they should all be updated together #6

@Exairnous

Description

@Exairnous

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:

  • certbotbot (workflow/repository not present yet)
    • PR:
  • coturn (workflow/repository not present yet)
    • PR:
  • dialog (workflow not present yet)
    • PR:
  • hubs
    • PR:
  • nearspark
    • PR:
  • pgbouncer (workflow/repository not present yet)
    • PR:
  • photomnemonic
    • PR:
  • reticulum
    • PR:
  • speelycaptor (workflow not present yet)
    • PR:
  • spoke
    • PR:
  • hubs-docs (for the centralized list of all repositories that contain this workflow/action)
    • PR:

Metadata

Metadata

Assignees

Labels

Tracking IssueLabel for issues that are used as a central place to coordinate larger pieces of work

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions