Git Operations
Every branch is a full git clone on its own git branch. Tarsk provides a Git Ops control in the chat dock footer so you can commit, push, and fetch without leaving the app.
The Git Ops Button
Section titled “The Git Ops Button”Git Ops sits in the bottom-left of the chat footer. It is a split button: the main label changes with git state (Commit, Create PR, etc.), and the chevron opens a dropdown with additional actions.
Status dots in the Branches list indicate:
- Brand dot — uncommitted local changes
- Orange dot — an open pull request exists (or needs updating)
- Animated dot — agent is processing in that branch
Main Button Actions
Section titled “Main Button Actions”| Label | When it appears |
|---|---|
| Commit | Uncommitted changes exist |
| Create PR | Committed and pushed, no open PR yet |
| Merge PR | An open pull request exists and is ready to merge |
Dropdown Operations
Section titled “Dropdown Operations”| Operation | Description |
|---|---|
| Sync with {branch} | Rebase your branch onto the latest default branch |
| Quick Commit | Generate an AI commit message and commit in one step (⌘⇧C) |
| Fetch | Download remote updates without merging |
| Pull | Pull latest changes from the remote branch |
| Push Branch to Remote | Create the remote branch and push (when no remote branch exists) |
| Push Commits | Push unpushed commits to the remote branch |
| History | View the commit log for this branch |
| Create Pull Request | Open the PR creation dialog (⌘⇧P) |
| Create Repo | Create a new GitHub repository from this branch |
| View in GitHub | Open the repository on GitHub (⌘⇧G) |
Use the Review dock panel to view diffs and revert individual files. Checkpoints are created automatically before agent runs and restored from the chat message header — not from this menu.
Committing Changes
Section titled “Committing Changes”- Click Commit on the Git Ops button (or Quick Commit in the dropdown).
- The commit dialog shows the number of changed files.
- Enter a commit message, or click Generate to have the AI write a conventional commit message based on the diff.
- Click Commit.
All modified and new files are staged automatically (git add -A) before committing.
AI-Generated Commit Messages
Section titled “AI-Generated Commit Messages”The Generate button sends the current diff to the AI model and returns a commit message following the conventional commits format (e.g. feat(auth): add JWT refresh token endpoint). You can edit the generated message before committing.
Pushing Changes
Section titled “Pushing Changes”- Click Push Commits or Push Branch to Remote in the Git Ops dropdown.
- Tarsk runs
git push -u origin <branch>to push the branch and set the upstream tracking reference. - A success message confirms the push.
If the push fails because the remote has commits you don’t have locally (non-fast-forward), run Fetch first, then resolve any conflicts before pushing again.
Fetching from Origin
Section titled “Fetching from Origin”Click Fetch in the Git Ops dropdown to run git fetch origin. This updates your local knowledge of what’s on the remote without modifying your working tree or current branch.
Creating a GitHub Repository
Section titled “Creating a GitHub Repository”If the branch doesn’t have a remote origin yet (e.g. you scaffolded a new app):
- Click Create Repo in the Git Ops dropdown.
- Enter the repository name and visibility (public/private).
- Click Create.
Tarsk runs gh repo create --source . --push, which creates the repository on GitHub, sets it as the remote origin, and pushes the current branch.
Viewing Git History
Section titled “Viewing Git History”Click History in the Git Ops dropdown to open a log of commits on this branch, showing commit hash, message, author, and date.
Syncing with the Default Branch
Section titled “Syncing with the Default Branch”Click Sync with {branch} in the Git Ops dropdown to pull the latest changes from the default branch (usually main or master) into your branch’s git branch using rebase.
Sync automatically:
- Pushes any unpushed commits on your branch first (if the branch has diverged)
- Runs
git pull --rebase origin <default-branch>to replay your commits on top of the latest default branch
If rebase conflicts occur, resolve them manually in your IDE, then continue the rebase.
Reverting a Single File
Section titled “Reverting a Single File”- Open the Review dock panel.
- Find the file you want to revert.
- Click Revert on that file’s diff.
Tarsk restores the file to its last committed state (HEAD). For untracked or newly staged files, the file is deleted from disk entirely.
Checkpoints
Section titled “Checkpoints”A checkpoint is a snapshot of the working tree before an agent run. Tarsk creates one automatically before the agent starts making changes (using git stash internally).
Restoring a Checkpoint
Section titled “Restoring a Checkpoint”- Find the user message in the chat that triggered the run.
- Click Restore checkpoint on that message.
- Confirm in the dialog.
This is destructive — all uncommitted changes and conversation messages since the checkpoint are lost.
Keyboard Shortcuts
Section titled “Keyboard Shortcuts”| Action | Shortcut |
|---|---|
| Open Git Ops menu | ⌘⇧B |
| Quick Commit | ⌘⇧C |
| Create Pull Request | ⌘⇧P |
| View in GitHub | ⌘⇧G |
Quick Commit only appears when uncommitted changes exist and auto-generate commit messages is enabled. Create Pull Request requires commits ahead of the default branch with no open PR.
Commit Method
Section titled “Commit Method”Whether changes go through pull requests is controlled by the project’s Commit Method setting in Project Settings:
- Pull Request — feature branches and PR workflow via
gh - Direct — commits and pushes to the branch directly