Integration
GetFlowing works inside your GitHub.
GitHub is the system of record for your code, and GetFlowing treats it that way. The platform installs as a GitHub App, works on branches in repositories you already own, and asks for a review the same way a colleague would.
Integration
GitHub integration
How it works
You install the GetFlowing GitHub App on your organisation and choose which repositories to manage. Repositories stay in your account. Agents implement work on a branch and open a reviewable pull request with test results attached, and commits, pull requests and workflow runs are read to give that work the context of your codebase.
The path
From installation to a merged change.
The path a change takes is the path your team already knows, which is what makes the work reviewable rather than opaque.
Install
Add the GetFlowing GitHub App to the organisation that holds the repositories you want managed.
Import
Choose repositories to manage. GetFlowing maps the stack, environments and deployment history and creates a managed project.
Plan
Work is described and agreed before implementation starts, so the change in the pull request is not a surprise.
Implement
An agent works on a branch in your repository and opens a pull request describing what changed and why.
Review
You read the diff and the attached test results, ask for changes if needed, and merge when you are satisfied.
Release
The container image is built and deployed, with production deployments pausing for approval and recorded in the audit trail.
Specification
The integration, stated plainly.
Deliberately narrow. The integration makes GetFlowing a contributor to your repositories rather than a new home for them.
- Installs as
- A GitHub App on the organisation that holds the repositories you want managed.
- Code location
- Repositories stay in your GitHub account. Importing one creates a managed project without copying or relocating the code.
- Change delivery
- Agents implement work on a branch and open a reviewable pull request. Nothing reaches your default branch without a human merge.
- Test results
- Attached to the pull request for that change, before it can be merged.
- Read for context
- Commits, pull requests and workflow runs, so the work fits the codebase and the conventions your team already follows.
- Monorepos
- Applications inside a monorepo are detected and related services stay grouped, rather than a repository being treated as one opaque unit.
- Your review rules
- Pull requests appear in GitHub, so existing required checks, branch protection and review habits still apply.
- Approvals
- Merging is your decision. Production deployments, migrations and secret changes pause again for a human, and every decision is recorded.
- Existing projects
- Importing software you already run is a first class path, included from the Pro plan upwards, and it preserves your stack, history and repository ownership.
- If you leave
- Nothing has to move back. The repository, its history and its permissions were never anywhere else.
Private beta
Bring software delivery into one system.
Build something new or take control of what already exists. Get the planning, engineering, deployment, and operational capability of an experienced software team.