Github actions are missing a vital piece of the CI/CD puzzle: the ability to build workflows in downstream projects.
These actions overcome this by using an otherwise empty repository as a record of what the dependencies are between projects and allowing downstream projects to register what their dependencies are and upstream projects to build them when they are complete.
It does not handle circular dependencies or create the most optimal graph of dependency building. It is recommended to do this by using the register-dependencies action judiciously.
Required The repository being used for orchestration
Required SSH key to use for accessing orchestrator
Required Token to use for accessing orchestrator and downstream workflows
uses: actions/github-dependencies/[email protected]
with:
orchestrator: ssh://[email protected]/YourOrg/orchestrator-repo
ssh-key:
Required The repository being used for orchestration
Required The list of newline separated repositories that will be registered as upstream of the calling repo
Required The name of the workflow to run (relative to .github/workflows)
Required SSH key to use for accessing orchestrator
uses: actions/github-dependencies/[email protected] with: orchestrator: ssh://[email protected]/YourOrg/orchestrator-repo ssh-key: ${{ secrets.ssh-key }} dependencies: | https://github.com/YourOrg/repo-1 https://github.com/YourOrg/repo-2
- Currently if the workflow registered with register-dependencies changes, it won't be updated correctly