Git Integration

DevFlow integrates with Git to track all code changes associated with a flow. Branches, commits, and pull requests are linked directly to flows, giving you a clear trail from requirement to merged code.

Branch Creation

When the agent starts working on a flow, it creates a Git branch following your project’s naming convention. The default pattern is:

feature/<display-id>-<slug>

For example, a flow with display ID DF-42 and summary “Add user login page” would produce:

feature/DF-42-add-user-login-page

You configure the branch naming pattern in your project’s Git settings. The agent follows this pattern automatically for every flow.

Commit Tracking

Every commit the agent creates is recorded in the flow. The flow detail view shows:

• Commit hash — The full Git commit hash
• Commit message — What was changed in this commit
• Timestamp — When the commit was created

This gives you a chronological record of how the implementation progressed, commit by commit. You can click through to your Git provider to see the full diff for any commit.

Pull Request Creation

When the agent finishes implementing a flow, it can create a pull request automatically. The PR includes:

• A descriptive title based on the flow summary
• A body with a summary of changes, testing instructions, and links back to the flow
• The correct target branch (see below)

The PR URL is recorded in the flow, so you can navigate directly from DevFlow to the pull request for code review.

PR Targeting

Pull requests are automatically targeted based on your release configuration:

• If a release is active — The PR targets the release branch
• If no release is active — The PR targets main (or your default branch)

This means you do not have to think about which branch to target. DevFlow handles it based on your current release state.

Git Settings

Each project has its own Git configuration. You can set this up when creating a project or update it later in the project settings. The available options include:

Branch Naming Convention

Define the pattern for branch names. You can use variables like:

• <display-id> — The flow’s display ID (e.g., DF-42)
• <slug> — An auto-generated slug from the flow summary
• <type> — The flow type (feature, bug, chore)

Commit Conventions

Configure how commit messages should be formatted. The agent follows these conventions when creating commits during implementation.

PR Templates

Set up templates for pull request descriptions. The agent uses these templates when creating PRs, filling in the relevant details from the flow.

Copy-Ready Commands

The flow detail view includes copy-ready commands that you can paste directly into your terminal. These are useful when you want to work on a flow yourself or alongside the agent:

• Branch name — Ready to copy for git checkout -b
• Claude Code command — A pre-built command to start the agent on this flow

Click the copy icon next to any of these to put them on your clipboard.

Release Branches

When you create a release in DevFlow, you can assign it a dedicated branch. All flows assigned to that release will have their PRs targeted at the release branch instead of main.

This supports a clean release workflow:

1. Create a release with a branch (e.g., release/v1.2.0)
2. Assign flows to the release
3. The agent creates PRs targeting the release branch
4. When all flows are complete, merge the release branch to main

See Releases for more information on release management.

How It All Connects

Here is how Git activity flows through DevFlow:

1. Flow created — No Git activity yet
2. Planning approved — Agent creates a branch following your naming convention
3. In progress — Agent creates commits, each tracked in the flow
4. Review submitted — Agent creates a PR targeting the correct branch
5. Review approved — PR is ready to merge, flow moves to done

Every step is visible in the flow detail view, giving you full visibility from the initial idea through to the merged code.