Branches

The Branches tab groups everything that is not a commit: branches, tags, remotes, stashes, worktrees and the repository-level switches for bisect, submodules, sparse checkout, hooks and LFS. Each opens as its own panel; the tab itself stays available while an operation runs.

Branches

• Create a branch at HEAD or at any commit.
• Switch by double-clicking, or from the branch header in the workbench.
• Delete one or several local branches. A multi-select delete reports per-branch outcomes. Unmerged branches are refused by default; a force delete is available and confirmed explicitly.
• Delete with remote removes the branch on the selected remote as well as locally.
• Merge with a choice of default, --no-ff or --squash.
• Merge preflight runs git merge-tree first: it lists the files that would conflict and the ahead/behind counts before the working tree is touched. Cancelling leaves the repository exactly as it was.
• Copy the branch name or a forge link.
• The detail view shows recent commits, upstream and ahead/behind.

An in-progress merge, rebase, cherry-pick or revert is reported in the workbench banner, with continue and abort actions. Abort writes a recovery snapshot of the working tree first.

Tags

• Create lightweight or annotated tags at a commit, with an optional message.
• Verify signatures: GPG and SSH tags are checked by Git and shown with the same good/bad/untrusted states as commits.
• Rename, delete, multi-delete and copy a forge link.
• Fetch tags explicitly when a remote has new ones.

Remotes

Add, edit, rename and delete remotes. URLs are shown in full; credentials embedded in a URL are not persisted by the application. Fetch and push use the system git, so credential helpers, SSH keys and proxy settings are the ones configured on your machine.

Stashes

• Create a stash with an optional message; include untracked files, or stash only the staged changes.
• Restore with or without restoring the index.
• Create a branch from a stash.
• Preview a file version inside a stash, restore individual files, or restore selected hunks from a stash.
• Stash selected hunks from the working tree, leaving the rest in place.
• Drop one stash or several at once. Each drop writes a recovery snapshot first.

Stashes are local to the repository and are not pushed anywhere.

Worktrees

• List worktrees with their path, branch, lock state and staleness.
• Open a worktree from its row; it becomes a repository tab in the current window. The repository that is already open is not opened a second time.
• Create a worktree at HEAD or at any commit, on a new or existing branch.
• Move, lock, unlock and repair a worktree.
• Detect a worktree whose directory disappeared and remove it.
• Remove several worktrees in one action, with per-worktree outcomes.

Bisect

• Start a bisect with a known-good and known-bad revision; recent commits are offered as good candidates.
• Run a command automatically: the command streams its output, its exit code marks each commit good or bad, and the run can be cancelled without losing the bisect state.
• Outside the automated run, mark the current commit good, bad or skip by hand.
• When the first bad commit is found, open it directly from the result.
• Reset the bisect when you are done.

The command runs with the repository as the working directory and inherits the environment the application was started with. It is your command, not a built-in check.

Submodules

• List submodules with their path, URL, recorded commit and status.
• Update from the remote in one action.
• Open a submodule as its own repository tab.
• Initialize and update as Git would, with the same ordering and the same failure modes.

Submodule operations can be slow on a cold clone; progress appears in Git Output.

Sparse checkout

Enable sparse checkout and edit the pattern set, or disable it to materialise the full tree. Changes apply to the current worktree only. The Files tab shows the files that are actually present; a path excluded by the sparse patterns does not appear until it is checked out.

Hooks

• List the hooks Git would run, whether each is enabled, and where it points.
• Edit a hook in the in-app text editor, with an explicit save.
• Toggle a hook by making it executable or not.
• Install a sample hook and adapt it.

Hook output appears in Git Output while the triggering command runs. Hooks run with your permissions, exactly as in a terminal.

LFS

• Show whether LFS is in use, installed and up to date.
• List, lock, unlock and force-unlock paths.
• View and edit LFS patterns.
• Pull LFS objects for the current checkout when files are still pointers.

git-lfs must be installed separately; the application uses the binary on PATH.

Next

• Conflicts — what a merge or rebase stops on.
• Sync — fetch, pull, push and force-with-lease.
• Workspace — all repositories at once.