Skip to content
GitTree
العربية

GitTree Docs

How to use GitTree

New to GitTree? Start with step 1 below. Already set up? Search for a task or pick a topic: every guide shows where to click and what you should see.

Start with step 1Browse topics
The GitTree window with the left panel, the toolbar, the commit graph and the inspector numbered

Every capture in these docs is the real GitTree interface, in English and in Arabic.

Start here

Get started in five steps

Follow them in order, from installing GitTree to your first commit. Each step is one short guide.

  1. Install GitTree

    Download the installer for your system, install it and open the app.

  2. Connect Git

    GitTree uses your own Git, 2.39 or newer, and the name and email your commits carry.

  3. Find your way around

    The tab bar, toolbar, sidebar, commit graph, inspector and status bar, and what each one does.

  4. Open a repository

    Open a folder you already have, or clone one from GitHub, GitLab, Bitbucket, Azure DevOps or any Git server.

  5. Make your first commit

    Stage a change, type a summary and press Commit: the new commit appears at the top of the graph.

Browse by topic

Find any task

Two manuals: the desktop app, section by section, and your account, teams and billing on gittree.app.

Desktop app

The desktop app, section by section. Each guide is one task: what you need first, where the control lives, numbered steps with the real interface, the result and how to recover.

Open the GitTree desktop manual

Account and teams

Everything on gittree.app: signing in from the site and the app, your profile and settings, organizations and their members, your plan and payments, and support tickets.

Open the GitTree account and teams manual

Popular tasks

What most people come for

The guides readers open most once they are set up.

  1. Changes and commitsStage files, hunks and selected linesA commit contains only what you stage. In GitTree you stage a whole file, one hunk of it, or just the lines you pick in the diff, and the rest of your edits stay in the working folder for a later commit.
  2. Merge and resolveResolve merge conflictsA conflict happens when both branches changed the same lines. GitTree’s resolver shows the two versions side by side, A and B: tick the lines to keep in each conflict, check the Output, then Save and continue the merge, rebase or cherry-pick.
  3. History and recoveryUndo and redoGitTree 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 refs/ogt/trash before they run.
  4. History and recoveryEdit history with an interactive rebaseAn 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 git rebase -i. For a single change, Edit History in a commit’s menu does it in one step.
  5. Remotes and syncFetch, pull and pushFetch 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.
  6. Branches and tagsCreate and switch branchesA branch is a movable name for a line of work. In GitTree, Branch in the toolbar creates one at the commit you are on; right-click any commit to create one there. Double-click a branch label to switch to it.
  7. Merge and resolveCherry-pick and revert commitsCherry-Pick Commit copies the changes of one commit onto your current branch as a new commit, like git cherry-pick. Revert Commit adds a new commit that undoes one, like git revert: the safe way to take back something already pushed.
  8. Stashes and worktreesStash changesA stash puts your uncommitted changes aside and gives you a clean working folder, like git stash, so you can switch tasks and bring the changes back later. Stash in the toolbar saves everything; the changes panel’s Stash tab chooses exactly what.
  9. History and recoveryReset a branch to a commitResetting moves your current branch to another commit, like git reset. Soft keeps every change staged, Mixed keeps them in your working folder, Hard discards them. GitTree saves everything under refs/ogt/trash first, so even a hard reset can be undone.
  10. Merge and resolveContinue, skip or abort an operationA merge, rebase, cherry-pick or revert can stop halfway, usually on a conflict. A banner above the graph names the operation and its step, and offers Resolve, Continue, Skip (rebase) and Abort…. Aborting saves what it drops first, so Undo brings it back.