Use repository maintenance and author tools
Repository Maintenance… shows the size of the object database and runs tasks that check it or make history and status faster. Merge Author Identities… writes .mailmap lines so one person with several names or e-mails shows as one author.
Works in GitTree Free: every local Git feature, once you are signed in.
On this page
Before you start
- A repository open in GitTree. Nothing runs until you start it.
Where to find it
- The command palette: Repository Maintenance… and Merge Author Identities….
| Action | macOS | Windows and Linux |
|---|---|---|
| The command palette | ⌘⇧P | Ctrl+Shift+P |
Steps
Read the counts
Open Repository Maintenance…. Object database shows its Size on disk, Loose objects, Packs and any Stray files.
Check integrity
Check under Check integrity runs
git fsckto look for missing or damaged objects. It changes nothing.Speed things up
Run the tasks you need from the table below. Each says what it changes before you run it.
Expected result
The repository is checked and its history, references and status load faster.
Maintenance tasks
| Task | What it does |
|---|---|
| Speed up history | Writes the commit-graph file, so the graph and history load faster. |
| Keep the commit-graph fresh | Sets fetch.writeCommitGraph=true, so every fetch updates it. |
| Pack references | Moves loose branch and tag references into one file. |
| Speed up status | Sets core.untrackedCache=true and builds the cache. |
Merge Author Identities…: choose Keep this identity, then the identities that are the same person under Show these as the kept identity, and press Merge Identities. Commit .mailmap to share it.
If something goes wrong
“The object counts could not be read.”
Close other programs using the repository and open the dialog again; run Check integrity if it persists.
Questions
Does .mailmap rewrite history?
No. It only changes how names are shown; every commit keeps the author it was made with.