Supported Git Repositories
Operator integrates with Git hosting platforms to manage branches and pull/merge requests.
Prerequisites
All providers require:
| Requirement | Purpose | Verification |
|---|---|---|
git |
Version control operations | git --version |
Available Integrations
Statuses follow the feature maturity scale; see Provider Support for the full tier table and architecture.
| Platform | Status | CLI Tool | Notes |
|---|---|---|---|
| GitHub | Beta | gh |
Full PR integration |
| GitLab | Alpha | glab |
Full MR integration |
| Gitea | Alpha | tea |
Full PR integration via tea api |
Provider Auto-Detection
Operator detects your Git provider from the remote URL automatically. You can override this in config:
[git]
provider = "github" # or "gitlab", "gitea"
Shared Git Configuration
These settings apply regardless of provider:
[git]
branch_format = "{type}/{ticket_id}" # Branch naming pattern
use_worktrees = false # Per-ticket worktree isolation
Branch format variables: {type} is the ticket type prefix (e.g., feature, fix, spike, investigation), {ticket_id} is the ticket identifier.
Worktrees: When enabled, Operator creates isolated git worktrees per ticket, allowing parallel development without branch switching.
How It Works
When an agent completes work on a ticket:
- Branch: Creates a feature branch from main
- Commit: Commits changes with ticket reference
- Push: Pushes branch to remote
- PR/MR: Opens a pull request or merge request for review
Local Git
Even without platform integration, Operator manages local Git operations:
- Branch creation and checkout
- Commit formatting with ticket IDs
- Branch cleanup after completion
- Worktree management for parallel development
Local git operations require only the git binary-no provider CLI or tokens needed.
Adding Provider Support
See the Provider Support guide for architecture details on implementing new providers.