GitTree desktop manual
Remotes and sync
Share your work and pick up your team’s: fetch, pull and push, and what the ahead and behind numbers mean.
Fetch, pull and push
Fetch downloads what is new on your remotes without changing your work. Pull brings your branch’s upstream into it. Push sends your commits to the remote. All three are in the toolbar, with their options in the arrow menus beside them.
FreeAdd and edit remotes
A remote is a named copy of the repository elsewhere, such as
Freeoriginon GitHub. The Remote section of the left panel lists them; Add Remote… adds one, and right-clicking a remote edits, fetches, prunes or removes it.Choose remote credentials
GitTree runs your own Git, so fetch, pull and push sign in the way Git does on your computer: over HTTPS through your credential helper, over SSH with your key or SSH agent. Passwords and tokens stay in your system keychain, never in GitTree’s files.
FreeConfigure automatic fetching
Auto-fetch keeps the remote branches in your graph current without you pressing Fetch All. Set the Auto-fetch interval in minutes for every open repository, override it for one repository, and get a desktop notification when new commits arrive.
FreeUse a force push with lease
After you amend, rebase or reset commits you already pushed, a normal push is refused. Force Push (With Lease)… replaces the remote branch with yours, but only if it is still where you last fetched it, like
Freegit push --force-with-lease. GitTree never force-pushes any other way.Work with limited repository history
A shallow clone downloads only the latest commits; a blobless clone downloads file contents only when needed. Both make huge repositories quick to clone. In a shallow clone the graph shows where history stops, and Fetch More History or Fetch Full History bring the rest.
Free