Install with one command
The installer detects Debian-based, RPM-based, and Arch-based distributions. It downloads the matching package from the public GitHub release, verifies its SHA-512 checksum, and invokes the system package manager with its normal confirmation prompt.
On other distributions, it installs an AppImage for the current user under ~/.local/opt/git-workbench and adds a desktop entry. Review the installer source before running it if you want to inspect the script.
curl -fsSL https://gitworkbench.github.io/install.sh | bashChoose a download manually
The downloads page lists the stable release, file sizes, and direct GitHub asset links. Choose a package that matches the distribution rather than an extension that merely looks familiar.
- Debian and Ubuntu: choose the .deb package.
- Fedora, RHEL-family systems, and openSUSE: choose the .rpm package.
- Arch and CachyOS: choose the .pkg.tar.zst package.
- Other distributions: use the x86_64 AppImage.
Update using the app or your package format
Packaged builds can check for updates in About → Software updates. AppImage, Debian, RPM, and Pacman builds support downloads and installation; package-manager installs may request system authorization.
For older installations with incorrect updater package markers, download the current package and upgrade manually. On Arch, install the downloaded Arch package using pacman -U. A failed authorization dialog is separate from an update check or download failure.
sudo pacman -U ./git-workbench-<version>-<pkgrel>-x86_64.pkg.tar.zstKeep installation and source builds separate
The released desktop package needs system Git. Node.js, Python, make, and a C++ compiler are prerequisites for building the source, not for installing a released Linux package.
If a release will not start, include the distribution, architecture, app version, package format, and the visible error when opening an issue. Check the current release notes for fixes before attempting a source build.