ActionsManager Product Demo

See a complete multi-repository GitHub Actions workflow rollout, start to finish, in ActionsManager Self-Hosted.

Table of contents
  1. Watch the demo
  2. What’s in the video
  3. What this demonstrates
  4. Next steps

Watch the demo

Watch on YouTube ↗

Can’t load the embedded player above? Watch it directly on YouTube instead:

ActionsManager product demo thumbnail - click to watch on YouTube

What’s in the video

The demo walks through a complete rollout to a multi-repository Maven project:

  1. Authenticate using a GitHub PAT — sign in with a fine-grained or classic personal access token.
  2. Create the MavenBuilds Caller Workflow Project — set up a project to manage a group of repositories.
  3. Add three repositories — bring the target repos under management.
  4. Detect the Maven build type — ActionsManager inspects each repository and identifies its build type.
  5. Generate workflow changes and create pull requests — a caller workflow is generated per repository and proposed as a pull request.
  6. Manage the pull requests — review and track PR status for all three repositories from one place.
  7. Merge the pull requests — apply the workflow changes to each repository.

Never expose a Personal Access Token in recordings, screenshots, shell history, documentation, or committed files. This demo does not require you to provide a PAT to YouTube or any third-party service — PAT authentication happens only between your browser and your own ActionsManager instance.

What this demonstrates

  • Multi-repository project management — grouping repositories under one Caller Workflow Project
  • Automated build detection — identifying a repository’s build type without manual inspection
  • Consistent workflow generation — the same workflow template applied uniformly across every repository
  • 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 interface
  • Workflow synchronization after merge — keeping caller workflows aligned with the managed definition once merged

Next steps