Changed files and their diffs, stage and commit.
Changed files carry a badge: M modified, U new, A staged new, D deleted, R renamed,
! in conflict. A folder with changes inside gets a dot. The branch chip in the path bar shows the
branch, ↑ commits to push and ↓ to pull, and how many files changed.
⇧⌘U (or a click on the chip) opens Review Changes: files beside their diffs, refreshing every
two seconds while you or a coding agent works. Burrow never takes git’s lock, so it can’t block an
agent’s or editor’s git.
- ↑↓ moves between files, Space stages one, A stages them all.
- ⌫ (or right-click ▸ Discard Changes…) throws a file’s changes away. Your version goes to the
Trash first, so ⌘Z brings it back.
- ↩ writes the message, ⌘↩ commits. Tick Amend last commit to fold the change into the
previous commit instead. Don’t amend one you’ve already pushed.
Hide Git-Ignored Files (⌘K) hides ignored files; otherwise they’re shown dimmed.
See also Branches, pull and push and Git history.
Switch or make branches, pull, push, fetch and stash.
Right-click the branch chip, or use the buttons at the top of Review Changes:
- Pull brings in new commits. When both your branch and the remote have moved on, Burrow asks
whether to Rebase (yours on top of theirs) or Merge.
- Push sends your commits. A branch that’s never been pushed is published to origin and set
to track it.
- Fetch checks the remote without changing anything, and updates the ↓ count.
- Switch Branch… lists branches, most recently used first. Type to filter, then ↩ to switch.
New Branch… makes one from where you are, and your changes come along.
- Stash Changes puts your changes (new files too) aside and leaves a clean copy.
Apply Latest Stash, or the ⋯ menu in Review Changes, brings them back.
Each one is also in ⌘K as Git: …. They use your own git setup, so SSH keys and saved passwords
work as they do in Terminal. These are the only times Burrow goes online, and only when you ask.
Merge conflicts: when a merge, rebase or cherry-pick stops on a conflict, Review Changes shows
a banner. Right-click a conflicted file to choose Use My Version or Use Their Version. Or
edit the file, then choose Mark as Resolved. Then click Continue, or Abort to go back
to how things were.
Every commit, and what it changed; a file's own history.
In Review Changes, switch to History to see the commits on your branch, newest first.
Click one (or use ↑↓) to see what it changed, file by file.
To see the history of one file, select it and choose Git: History in ⌘K. Or right-click it in
Review Changes and choose History of This File. Renames are followed. Click the × on the
file’s name to go back to the whole repository.
Cursor, VS Code, Zed, Xcode; Terminal, Ghostty, iTerm…
⇧⌘E opens the selection (or the folder) in your code editor; ⌘K ▸ Open in Terminal opens
your terminal app there. Pick them in Customize ▸ General ▸ Apps.