Fleet provides Git and GitHub workflow management for registered apps. All GitHub operations use the gh CLI over HTTPS.
fleet git status
Show the git state for one or all apps.
Usage
fleet git status [app] [--json]
Arguments
| Argument | Required | Description |
|---|
app | No | App name. Omit for all apps. |
Examples
APP BRANCH STATE ONBOARDED
branch: main | branches: main, develop
remote: https://github.com/org/myapp.git
onboarded: 2025-01-15T10:00:00.000Z
- MCP tool:
fleet_git_status
fleet git onboard
Create a GitHub repository for an app, push the code, and configure branch protection rules.
Usage
fleet git onboard <app> [--dry-run] [-y]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
Flags
| Flag | Description |
|---|
--dry-run | Show the onboarding plan without making changes |
-y, --yes | Skip confirmation prompt |
Examples
$ fleet git onboard myapp --dry-run
Onboard plan: myapp (fresh-repo)
3. gh repo create org/myapp --private
5. Create and push develop branch
6. Enable branch protection on main and develop
dry run - no changes made
$ fleet git onboard myapp -y
✓ Pushed main and develop
✓ Branch protection enabled
repo: https://github.com/org/myapp
- MCP tool:
fleet_git_onboard
fleet git onboard-all
Onboard all apps that have not yet been onboarded to GitHub.
Usage
fleet git onboard-all [--dry-run] [-y]
fleet git branch
Create a feature branch from a base branch and push it to origin.
Usage
fleet git branch <app> <name> [--from <branch>]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
name | Yes | New branch name |
Flags
| Flag | Description |
|---|
--from <branch> | Base branch to create from (default: develop) |
Examples
$ fleet git branch myapp feat/new-feature
✓ created and pushed branch feat/new-feature from develop
$ fleet git branch myapp fix/bug --from main
✓ created and pushed branch fix/bug from main
- MCP tool:
fleet_git_branch
fleet git commit
Stage all tracked changes and commit.
Usage
fleet git commit <app> -m "message" [--dry-run]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
Flags
| Flag | Description |
|---|
-m "message" | Commit message (required) |
--dry-run | Show what would be committed without writing |
Examples
$ fleet git commit myapp -m "feat: add new endpoint"
✓ committed: feat: add new endpoint
- MCP tool:
fleet_git_commit
fleet git push
Push the current branch to origin.
Usage
fleet git push <app> [--dry-run]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
Examples
✓ pushed feat/new-feature
fleet git pr create
Create a pull request on GitHub from the current branch.
Usage
fleet git pr create <app> --title "..." [--base <branch>] [--dry-run]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
Flags
| Flag | Description |
|---|
--title "..." | PR title (required) |
--base <branch> | Target branch (default: develop) |
--dry-run | Show what would be created |
Examples
$ fleet git pr create myapp --title "feat: add new endpoint"
✓ created PR #42: https://github.com/org/myapp/pull/42
- MCP tool:
fleet_git_pr_create
fleet git pr list
List open pull requests for an app.
Usage
fleet git pr list <app> [--json]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
Examples
$ fleet git pr list myapp
Pull Requests: myapp (2 open)
#42 feat: new endpoint feat/new-endpoint -> dev https://...
#40 fix: bug fix fix/bug -> develop https://...
- MCP tool:
fleet_git_pr_list
fleet git release
Create a pull request from develop to main (release PR).
Usage
fleet git release <app> [--title "..."] [--dry-run]
Arguments
| Argument | Required | Description |
|---|
app | Yes | App name |
Flags
| Flag | Description |
|---|
--title "..." | PR title (default: Release: <app>) |
--dry-run | Show what would be created |
Examples
$ fleet git release myapp
✓ created release PR #50: https://github.com/org/myapp/pull/50
$ fleet git release myapp --title "Release v1.2.0"
✓ created release PR #50: https://github.com/org/myapp/pull/50
- MCP tool:
fleet_git_release