GitTree desktop manual
History and recovery
Change history you have not shared yet, step back when something went wrong, and find out where a line came from.
Edit history with an interactive rebase
An interactive rebase rewrites the commits above a chosen one: keep, reword, edit, squash, fix up or drop each, and drag them into a new order, like
Freegit rebase -i. For a single change, Edit History in a commit’s menu does it in one step.Squash commits
Squashing combines several commits into one, like a
Freefixuporsquashingit rebase -i. In GitTree every squash opens the Squash dialog first: it shows the commits that fold, the result, the message and who gets credit, and nothing changes until you confirm. Your uncommitted work is never touched, and Undo puts the commits back.Change selected local commits
For one quick change to history, you do not need the whole interactive rebase editor. A commit’s Edit History menu edits its message, drops it, or moves it up or down; selecting several commits opens the Squash dialog. GitTree rewrites the commits above it and keeps the old branch, so Undo puts it back.
FreeReset a branch to a commit
Resetting moves your current branch to another commit, like
Freegit reset. Soft keeps every change staged, Mixed keeps them in your working folder, Hard discards them. GitTree saves everything underrefs/ogt/trashfirst, so even a hard reset can be undone.Undo and redo
GitTree records your Git operations so Undo in the toolbar can take the last one back: a commit, merge, rebase, reset, discard, clean, deleted branch or tag. Redo does it again. Destructive steps save a recovery snapshot under
Freerefs/ogt/trashbefore they run.Find previous branch tips
The reflog records where a branch or HEAD pointed, every time it moved: commits, checkouts, resets, rebases. View Reflog… lists those entries; choose one to show its commit in the graph or Restore as Branch.
FreeFile history and blame
History lists every commit that changed a file, following renames, like
Freegit log --follow. Blame shows, for each line, the commit and author that last changed it, likegit blame. Both are views of the file workspace.Use the bisect workflow
Bisect finds the first commit that introduced a problem by halving the history between a commit that has it and one that does not, like
Freegit bisect. Select the two commits, test the commit GitTree checks out, mark it Good or Bad, and repeat until it names the First bad commit.Export an archive
Export Archive… writes the files of a commit, branch or tag as a .zip or .tar.gz, without the
Free.gitfolder, likegit archive. It is the quickest way to hand someone a release’s source.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
Free.mailmaplines so one person with several names or e-mails shows as one author.