I’ve been working on a self-hosted tool for managing GitHub Actions across multiple repositories, mostly because I was tired of maintaining the same workflow patterns repo by repo.
The main problem I’m trying to solve is keeping reusable workflows and their caller workflows consistent. ActionsManager tracks the managed workflow definition, shows which repositories have drifted, and can group updates into a PR campaign across the affected repositories.
It currently runs as a single Docker container and includes:
- Multi-repository project management
- Reusable and caller workflow management
- Workflow drift detection
- Build-type detection
- PR-based workflow rollouts
- Bulk PR management
The project is currently a free self-hosted public beta. I’m mainly looking for technical feedback from developers and platform engineers who manage GitHub Actions across a larger set of repositories.
Project: actionsmanager.io
GitHub: github.com/dawg-io/actions-manager
How are you handling this today? Internal tooling, scripts, Renovate, repository templates, or something else?
I’d also be interested in hearing where this approach would break down in a real platform-engineering environment.
Top comments (0)