Repository navigation
BitGit 1.3.0
Installation
Windows: Download and run BitGit_1.3.0_x64-setup.exe (NSIS installer) or BitGit_1.3.0_x64_en-US.msi (MSI installer)
macOS 11 or later: Download BitGit_1.3.0_aarch64.dmg (Apple Silicon) or BitGit_1.3.0_x64.dmg (Intel), open it and drag BitGit to Applications. This build is not signed or notarized by Apple, so macOS blocks its first launch: open BitGit once and close the warning, then choose Open Anyway under System Settings > Privacy & Security (System Preferences > Security & Privacy on macOS 12 and earlier) and confirm. BitGit needs Git (xcode-select --install) and Node.js 22 or later; see INSTALL.md.
Linux (AppImage only): Download bit-git_1.3.0_amd64.AppImage, make it executable (chmod +x) and run it. It needs FUSE 2 (libfuse2; libfuse2t64 on Ubuntu 24.04), Node.js 22 or later, Git, and a running Secret Service (GNOME Keyring, KWallet or KeePassXC) to store the GitHub token. The .deb and .rpm are no longer published: they need webkit2gtk 4.0, which current distributions do not ship. For a blank window on NVIDIA drivers, see INSTALL.md.
What's New
- GitLab and other Git hosts: a folder whose branch already tracks a remote (or has
origin) counts as connected, not Local Only. The card shows and links that remote, and Push, Sync Branch and the bulk actions work without a saved GitHub link. Remote URLs are stored without usernames or passwords - Labels: give a project up to eight labels, then filter the board by label or find projects by label in search
- Add Project > Import Folders: choose a folder, untick the repositories you don't want, and add the rest at once
- Open a terminal in a project's folder from its card (Terminal on macOS, Windows Terminal or Command Prompt on Windows, the installed terminal on Linux)
- Select All and Ctrl/⌘+A select only the projects the current filters show, so bulk actions never reach hidden projects
In 1.2.1
- Linking a project to an existing GitHub repository works again: the list shows each repository's owner, searching no longer closes it with an error, only the repository you pick is selected, and linking saves its URL. Thanks @zznam (#1)
- macOS: dashboard shortcuts use ⌘ (⌘R refresh, ⌘N new project, ⌘F search, ⌘A select all, ⌘D theme) and their hints say so; Ctrl still works
In 1.2.0
- macOS: builds for macOS 11 or later on Apple Silicon and Intel, with the GitHub token kept in the Keychain. The app is not signed or notarized by Apple; see Installation
- macOS and Linux: BitGit starts its Git service from the installed app and finds Node.js and Git through your login shell's PATH, even when opened from Finder, the Dock or a desktop menu
- macOS and Linux: projects inside a linked folder (such as macOS
/tmpor Fedora Atomic's/var/home) can be saved and recovered, and a timed-out fetch or push also stops its ssh or HTTPS helper - macOS: Git errors suggest
xcode-select --installwhen the Command Line Tools are missing, and VS Code, Cursor and Sublime Text open without their shell command - Linux: only the AppImage is published; the .deb and .rpm need webkit2gtk 4.0, which current distributions no longer ship. If you installed the 1.1.2 .deb, remove it with
sudo apt remove bit-gitand use the AppImage - Linux: saving the GitHub token without a Secret Service says which is missing
- Security: simple-git 4.0.2 fixes critical command-execution advisories in the Git service. Branch and tag names are validated, and cloning or linking accepts only HTTPS, SSH and
git://remote URLs - Editors start directly instead of through
cmd /Con Windows, and recoveries running in different projects each use their own GitHub token
Since 1.1.0
- Automatic updates: BitGit checks for a newer release at startup and offers to install it (Windows installers, the macOS app and the Linux AppImage)
- Save & Recover workspace: named milestones, byte-exact checkpoints, coverage and comparison, verified recovered copies, and selective file repair behind a safety checkpoint
- Remote checkpoint backup and import through GitHub, with remote trust and verification
- Explicit, scoped visual Git publishing: only selected whole files or committed changes are published, with honest status and validated tag pushes
- Automatic idle saves, exact-version notes, screenshots and checks, guided regression search, and a JSON harness CLI
- Analytics load from one local snapshot per repository; Git service requests run concurrently and a stopped service restarts on the next request
- One BitGit process per data directory; unhandled frontend errors surface as toasts; the Git service survives stray promise rejections
- Linux packages build again (wry 0.24.12); 1.1.0 shipped without them