Skip to content
Zide Zide Zide

Git Summary

Use the Git Summary tab to see the local repository’s storage, pending local work, and synchronization state, and to open its Git tools and maintenance actions.

To open the Git Summary tab, click Git > Git Summary, or open the Project Header’s Repository actions menu and click Git Summary. The tab belongs to the repository it was opened from, and opening it again brings that tab forward rather than making a second one.

Every Git tool tab carries a Git tools control beside its title. Use it to move between Git Summary, Remotes, Submodules, Subtrees, Git LFS, Sparse Checkout, Repository Config, and Hooks. The menu marks the tool you are on, and choosing a tool opens it for this repository, or brings its tab forward when it is already open. Each tool is its own tab, so two projects can each have their own.

Storage

The Storage table shows:

  • Path: The repository’s location on disk. Use the folder button to open it in your operating system’s file manager, or the copy button to copy the path.
  • Tracked files: The number of unique paths in Git’s index. This does not include ignored or untracked files.
  • Git database: The disk space used by the repository’s local Git database.

When applicable, Characteristics identifies a bare repository, linked worktree, partial clone and its filter, or a non-default object format. Ordinary repositories do not show a Characteristics row.

Local Work

The Staging shortcut summarizes staged, unstaged, and untracked files. It also reports conflicts when any are present. A file with both staged and unstaged edits contributes to both counts. Click the shortcut to select Staging in the activity bar and open its side panel.

The Stashes shortcut shows how many stashes the repository contains. Click it to select Stashes in the activity bar and open its side panel. Stashes are reported separately because they are saved local work, not changes in the current working tree.

Branches & Sync

The synchronization strip shows whether the current branch is up to date, ahead, behind, or diverged from its upstream. It also shows the last fetch time and tracked upstream when that information is available.

The counters show the repository’s local branches, remote-tracking branches, and worktrees. Click a counter to open the corresponding details.

Shallow clones

For a shallow clone, the Git Summary tab shows how many commits are available locally. Click Fetch Full History to complete the clone, or use its menu to fetch a specific number of additional commits.

Configuration

The Configuration shortcuts open Remotes, Submodules, Subtrees, Git LFS, Sparse Checkout, Repository Config, and Hooks. Each shortcut summarizes its current state, and each opens that tool’s own tab for this repository, or brings it forward when it is already open.

The Hooks shortcut counts only active hooks. Every repository has a hooks directory full of samples; only an executable hook actually runs.

The Subtrees shortcut distinguishes subtrees found in commit history from those that have the local configuration Zide needs for Pull and Push. For example, 3 detected, 1 configured means all three are listed in the Subtrees tab, but only one is connected to an upstream in this checkout.

Maintenance

Click Clean Untracked Files… to delete untracked files. You can also click Git > Clean Untracked Files….

The dialog lists the files and folders to delete. To include ignored files, such as build output, select Also include ignored files. The list updates, and the title changes to Clean Untracked and Ignored Files. Review the list, then type clean and click Clean. Zide permanently deletes the listed items.

When you select or clear Also include ignored files, Zide clears the confirmation text. Type clean again for the new list.

A large list can take time to load. To stop, click Cancel.

Zide keeps nested repositories, submodules, linked worktrees, the .zide folder, and folders that it cannot read or that are nested too deeply. The dialog lists these items under Kept. The .zide folder stores project data, including Zide Assist memories.

Zide deletes only items in the list. If a listed file changes after review, Zide keeps it. If new files appear in a listed folder, Zide keeps the folder and the new files. The result message tells you how many items Zide kept.

If you stage files or change branches after you review the list, Zide cancels the deletion. See The repository changed before an action could start.