Review, commit, and work with branches

From changed files to a commit

Use Add to Git on an untracked file in Changes, or select changed files and write a commit message. Commit drafts are kept per checkout, and Commit & push is available when you want both steps.

These are whole-file selections, not individual-hunk staging. Adding a file respects ignore rules and does not commit it by itself.

See where your branch is going

The Branches tab lets you browse local and remote branches, inspect history and multi-file patches, fetch, create branches, and switch between them. Push review makes the source and destination explicit before you send changes.

Pull is fast-forward only. This workbench covers specific Git workflows alongside your coding sessions, rather than replacing every Git command.

Resolve a local rebase in place

Start a rebase onto another local branch, then resolve text conflicts section by section. Choose either side, keep both, or edit the result before staging it. Whole-file choices handle binary files and deletions.

You can continue or abort an in-progress rebase after reloading. Abort asks for confirmation, and stale conflict versions block saving until refreshed. The rebase flow is local-only: it does not fetch or push for you.

Each session keeps its Files view

Switching sessions now restores that session’s Files tab, pinned checkout, and workbench view instead of sharing one selection across every conversation.