Skip to content

GitTree v2.2.4

Choose a tag to compare

View all tags
@eslamfaisal eslamfaisal released this 30 Oct 05:23
v2.2.4
26a2bbb

GitTree v2.2.4

What's new

GitTree 2.2.4 makes pull requests easier to prepare and review, with reviewer autocomplete, editable branches, formatting tools and clearer merge comparisons.

  • Find reviewers by name. Type a name to filter reviewer suggestions for GitHub, GitLab, Bitbucket or Azure DevOps. Select people by mouse or keyboard and remove selected reviewers with a click.
  • Choose both pull request branches. Change the From and Into branches in the pull request dialog. Pushes and generated descriptions follow the branches you select.
  • Format descriptions and reviews. Use a Markdown toolbar and preview to format pull request descriptions, comments and review summaries.
  • See what a merge changes. Preview the changes a merge brings in and compare a merge commit with either parent.
  • Close a repository tab with its close button on Windows.
  • A source branch becomes ready for a pull request only after its push succeeds.

الجديد في هذا الإصدار

يسهّل GitTree 2.2.4 إعداد طلبات السحب ومراجعتها، مع الإكمال التلقائي لأسماء المراجعين، واختيار الفروع، وأدوات التنسيق، ومقارنات أوضح للدمج.

  • البحث عن المراجعين بالاسم. اكتب الاسم لتصفية اقتراحات المراجعين في GitHub أو GitLab أو Bitbucket أو Azure DevOps. اختر الأشخاص بالفأرة أو لوحة المفاتيح، وأزل المراجعين المختارين بنقرة واحدة.
  • اختيار فرعي طلب السحب. غيّر فرعي المصدر والوجهة داخل نافذة طلب السحب. تتبع عمليات الدفع والأوصاف المُنشأة الفروع التي تختارها.
  • تنسيق الأوصاف والمراجعات. استخدم شريط أدوات Markdown والمعاينة لتنسيق أوصاف طلبات السحب والتعليقات وملخصات المراجعة.
  • معاينة تغييرات الدمج. عاين التغييرات التي يضيفها الدمج، وقارن إيداع الدمج بأي من الإيداعين السابقين له.
  • إغلاق تبويب المستودع بزر الإغلاق على Windows.
  • لا يصبح فرع المصدر جاهزًا لطلب السحب إلا بعد نجاح دفعه.

Download

Your computer File
macOS 13 or newer, Apple silicon and Intel Git-Tree-macOS.dmg
Windows 10 (22H2) and 11, 64-bit Git-Tree-Windows-setup.exe
Ubuntu 22.04 or newer, Debian 12 or newer, 64-bit (x86_64) Git-Tree-Linux.deb
Other Linux distributions, 64-bit (x86_64), glibc 2.35 or newer (portable) Git-Tree-Linux.AppImage

The same files are also attached with the version in their name (Git-Tree_2.2.4_universal.dmg, Git-Tree_2.2.4_x64-setup.exe, Git-Tree_2.2.4_amd64.deb, Git-Tree_2.2.4_amd64.AppImage). The download buttons on https://gittree.app always serve the newest release.

Windows via Microsoft Store (recommended). Get GitTree from Microsoft Store. Microsoft Store signs and distributes that edition and manages its updates. Store releases may become available at a different time from GitHub releases.

Install

macOS. Open the .dmg, drag GitTree into Applications, and open it.
This build is signed with an Apple Developer ID and notarized by Apple, so macOS opens it without a warning.

Windows. Run the installer and follow the steps (it installs for all users and asks for administrator approval).
The direct EXE is not code-signed yet and Windows may show a security warning. If Windows blocks it, use the Microsoft Store edition or ask your IT administrator. Store certification does not sign this separate EXE.

Linux (Ubuntu, Debian). GitTree needs Git 2.39 or newer. Ubuntu 24.04 and Debian 12 ship a new enough Git. Ubuntu 22.04 and Linux Mint 21 ship Git 2.34, so install a current Git from the git-core PPA first:

sudo add-apt-repository ppa:git-core/ppa
sudo apt update
sudo apt install git

Then install the package with apt, which also installs what it needs (Git and WebKitGTK):

sudo apt install ./Git-Tree-Linux.deb

GitTree then appears in your applications menu. Remove it with sudo apt remove git-tree. Your sign-in is kept in the desktop keyring through the Secret Service: GNOME Keyring, which is preinstalled on Ubuntu and recommended by the package, or KeePassXC with its Secret Service integration turned on. When Git asks for an HTTPS password or an SSH passphrase, GitTree shows the prompt with zenity or kdialog, which the package also recommends.

Linux (AppImage). Keep the file in a folder only you can write to, such as your home folder (not /tmp or a shared folder). Make it executable and run it: chmod +x Git-Tree-Linux.AppImage && ./Git-Tree-Linux.AppImage. Git 2.39 or newer must be installed (see the Ubuntu and Debian note above). If it does not start, or reports that no suitable fusermount was found, FUSE is missing: install it with sudo apt install fuse3. Only on a private, single-user machine, start it with ./Git-Tree-Linux.AppImage --appimage-extract-and-run instead. An AppImage does not register the opengittree:// link the browser uses to return to the app after you sign in (AppImageLauncher can add it), so when the browser cannot open GitTree, choose Manually enter authentication code in GitTree and paste the code the website shows.

The Linux packages are not signed by a distribution package authority. Each installer has a detached .sig file that GitTree verifies during in-app updates. For a manual download, compare its SHA-256 with SHA256SUMS.txt (below).

First launch

GitTree asks you to sign in with a free account on https://gittree.app (your browser opens, then returns to the app). To see pull requests and issues of your GitHub repositories in the sidebar, connect GitHub under Preferences > Integrations.

Verify the download

SHA256SUMS.txt lists the SHA-256 of every file. It is published in the same place as the files, so it catches a corrupt or incomplete download, not a compromised release. Compare the value for the file you downloaded:

shasum -a 256 Git-Tree-macOS.dmg                    # macOS
sha256sum -c --ignore-missing SHA256SUMS.txt        # Linux, in the download folder

On Windows: Get-FileHash .\Git-Tree-Windows-setup.exe -Algorithm SHA256.

Assets 23
Loading