Hi HN, I built ActionsManager after dealing with the difficulty of keeping GitHub Actions workflows consistent across multiple repositories.
It is a self-hosted application that groups repositories into projects, detects build types, manages workflow files, creates and manages pull requests across repositories, and detects when workflows have drifted from the managed version.
The current release is a free self-hosted beta. The quickest setup uses Docker and a GitHub personal access token.
I also recorded an end-to-end demo showing PAT login, creation of a project with three Maven repositories, build detection, pull request creation, PR management, and merging:
I am especially interested in feedback from people managing GitHub Actions across multiple repositories:
- Does this solve a problem you currently have?
- What would prevent you from trying it?
- Which parts of multi-repository workflow management are still missing?
It is a self-hosted application that groups repositories into projects, detects build types, manages workflow files, creates and manages pull requests across repositories, and detects when workflows have drifted from the managed version.
The current release is a free self-hosted beta. The quickest setup uses Docker and a GitHub personal access token.
I also recorded an end-to-end demo showing PAT login, creation of a project with three Maven repositories, build detection, pull request creation, PR management, and merging:
https://youtu.be/jbG-T6M-tko
I am especially interested in feedback from people managing GitHub Actions across multiple repositories:
- Does this solve a problem you currently have? - What would prevent you from trying it? - Which parts of multi-repository workflow management are still missing?