Product Demo
See a complete multi-repository GitHub Actions workflow rollout, start to finish, in ActionsManager Self-Hosted.
Watch the demo
Section titled “Watch the demo”This cut has no sound; a caption names each chapter as it starts. For a narrated version with captions, watch it on YouTube ↗. GitHub is simulated in both, so no real repository or account appears.
What’s in the video
Section titled “What’s in the video”The demo rolls one workflow out to three Node.js repositories, node-api, node-worker and node-web:
- Sign in with a personal access token (0:00): paste a fine-grained or classic PAT on the sign-in screen.
- Create a Caller Workflow Project (0:10): name it NodeBuilds, pick the three repositories, choose prefix mode and set the project key NODE.
- Detect the build type (0:31): add a workflow called
build-and-test. ActionsManager detects Node.js (npm) in all three repositories, so one workflow fits the whole project. Picking Node.js (npm) starts the workflow from that template, and it is committed locally as a draft. - Open pull requests across repositories (0:47): one PR campaign opens PRs #41, #42 and #43, one per repository, each adding
AM_NODE_build-and-test.ymlon theactions-manager/nodebuildsbranch. - Review and merge (1:06): Merge Open PRs merges all three from the campaign, which moves to Completed Campaigns.
What this demonstrates
Section titled “What this demonstrates”- Multi-repository project management: grouping repositories under one Caller Workflow Project
- Automated build detection: identifying each repository’s build type without manual inspection
- Consistent workflow delivery: one workflow definition delivered to every repository in the project
- PR-based delivery: proposing changes as reviewable pull requests instead of direct commits
- Centralized PR management: tracking and merging pull requests across repositories from one PR campaign
Next steps
Section titled “Next steps”© 2026 ActionsManager. All rights reserved.