Work with Git visually

Git TreeBeginner5 min

Git Tree brings repository history, branch state, working-tree changes and common Git operations into the same CodeZero workspace.

Read the Git graph

The main graph shows branch labels, commit relationships, commit messages, authors, dates and short commit identifiers. Uncommitted work appears above the history as a working-tree row.

Use it to understand:

How branches have evolved
Where branches diverged or merged
Which commits belong to each branch
Where your current work sits in the repository history

Git Tree showing the branch list, commit graph with authors and short hashes, and the Changes and Stashes sections — Git Tree · branch list, commit graph and the Compare and Blame actions.

Inspect working-tree changes

The working-tree row collects what is not committed yet. Open it to see the changed files, review each diff and decide what belongs in the next commit.

Stashes sit alongside it: create a stash to park work, then apply, pop or drop it when you come back.

Run one-click Git actions

Frequently used actions are available directly from the toolbar, including Refresh, Fetch, Pull, Push, Branch, Compare and Blame.

Additional Git workflows in the graph include branch checkout and management, tags, stashes, merges, fast-forward, rebase, resets and conflict resolution.

Destructive actions stay explicit. Branch deletion, rebase and reset ask for confirmation, and hard reset is called out as destructive before CodeZero will run it.

Drag and merge branches

Drag one branch onto another to initiate a merge. Before the merge runs, CodeZero confirms the source and destination. If the operation produces conflicts, resolve them before continuing.

Compare branches

Open Compare and choose a Base and Target. CodeZero shows the commits present in the target but not the base, along with the combined set of changed files.

Use the file list and additions/deletions counts to understand the size of the change before merging. Select a changed file when you need its diff.

Inspect a commit

Select any commit in the graph to inspect the files it changed, additions and deletions, commit message, author, authored and committed dates, and parent information.

Use blame and file history

Enable Blame from the toolbar, open a source file and select a line. CodeZero shows who last changed that line, when it changed and the commit it came from. Hover the inline blame when you need more commit detail.

Open file history when the question is about a single file rather than the branch. It lists the commits that touched that file, so you can see when behaviour changed and read the diff that changed it.

Together these are usually the fastest route from a surprising line of code to the change that introduced it.