Git Manager

History-first Git for the desktop.
Search the commit graph, review inline or side-by-side diffs, resolve conflicts,
and clone from GitHub, GitLab or Bitbucket. For Windows, macOS and Linux.

Website · Features · Install · Host accounts · Search · Keyboard · Build · Docs

_{The commit graph across all branches. Selecting a commit shows its files and diff in the inspector.}

Working tree Stage, unstage, discard, stash and commit, with an inline or side-by-side diff of each change.

Merge editor Jump from conflict to conflict and resolve each in place, with ours, the result and theirs colored and scrolling together.

Download the latest build from Releases:

Builds are not code-signed yet, so the first launch needs one extra step:

• Windows: if SmartScreen appears, choose More info → Run anyway.
• macOS: open the app with right-click → Open, or run xattr -cr "/Applications/Git Manager.app".
• Linux: make the AppImage executable (chmod +x Git-Manager-*.AppImage), or install the package with sudo apt install ./Git-Manager-*.deb.

On Windows and Linux the app then updates itself from the same releases. macOS updates need a signed build, so for now install new versions from the releases page.

• Windows 10 or 11, macOS on Apple silicon, or Linux x64
• System Git on PATH, or set GIT_MANAGER_GIT_PATH to a Git binary

The app probes for Git at startup and guides you to install it if missing.

Use Host accounts from the welcome screen, or Accounts in the app menu, to link GitHub, GitLab (GitLab.com or your own instance), or Bitbucket. The app uses OS secure storage when available and marks accounts whose tokens were stored without OS encryption. It lists remote repos so you can clone them (HTTPS or SSH).

1. Open Host accounts.
2. Choose a provider.
3. Paste a personal access token (for a self-managed GitLab, also enter its address; for Bitbucket: an Atlassian API token plus your Atlassian account email).
4. Click Connect.
5. Select an account in the list to load remote repositories, then Clone a repo.

Clone, fetch, and push still use your normal Git credentials: HTTPS via Git Credential Manager, SSH via your OpenSSH agent and keys. Connecting an account only unlocks browsing and one-click clone from the host listing.

More detail: docs/features/host-accounts.md.

To review a whole feature branch, use Compare… above History, enter a base and target, and leave Changes since common ancestor checked. Uncheck it to compare exact snapshots. A commit's actions menu also offers Compare with HEAD…. Reference comparison explains the modes.

Type in the search box above the history and press Enter. Search runs in Git across all branches, unless you narrow it:

While you type, matching branches are suggested: ↑ / ↓ to pick one, Enter to show that branch, Alt+Enter (Option+Enter on macOS) to jump to its tip. Each branch in the sidebar also has Show only this branch and Jump to tip.

More detail: docs/features/history-graph.md.

Repository → Remotes & Publishing… adds or edits remote URLs, changes branch tracking and publishes the current branch to a selected remote/destination branch. The server repository must already exist. Fetch to load its branches before choosing an upstream. See Remotes & publishing.

Commit messages restore after switching views or repositories and after restarting. Successful commits clear their draft; failed commits keep it.

Repository → Recovery… (also above History) lists previous commits and tracked-change snapshots saved before amend, reset, rebase, branch deletion and tracked discard. Create a branch to recover a commit. Restore a snapshot onto a clean working tree/index to recover staged and unstaged edits. Untracked files discarded from Changes are in the Trash. See Recovery for limits and retention.

The app remembers its last maximized/full-screen mode. On startup, it opens saved repositories directly; repository setup appears when the saved list is empty.

Menu shortcuts use Ctrl on Windows and ⌘ on macOS:

Requires Node.js 22 and Git.

npm install
npm run dev

npm test
npm run typecheck
npm run lint

npm run dist        # current platform
npm run dist:win
npm run dist:mac
npm run dist:linux

Pushing a v* tag that matches package.json runs .github/workflows/release.yml: it builds all three platforms and publishes the release with the built-in GITHUB_TOKEN after the required Windows and macOS jobs succeed; Linux is optional. Release notes come from docs/releases/<version>.md when present. Signing is optional: add MAC_CSC_LINK, MAC_CSC_KEY_PASSWORD and APPLE_ID, APPLE_APP_SPECIFIC_PASSWORD, APPLE_TEAM_ID for a notarized macOS build, or WIN_CSC_LINK, WIN_CSC_KEY_PASSWORD for Windows. Without them macOS builds are ad-hoc signed. See release preparation and the 1.2.0 release notes. The website in site/ deploys through .github/workflows/pages.yml.

flowchart LR
  subgraph renderer [Renderer]
    UI[App + shell + features]
  end
  subgraph bridge [Preload]
    API["window.gitManager"]
  end
  subgraph main [Main process]
    IPC[ipc handlers]
    Store[userData state]
    Prov[providers]
    Upd[updater]
  end
  subgraph git [Git worker]
    Runner[runGit]
    Ops[ops/*]
  end
  UI --> API
  API -->|ipcRenderer.invoke| IPC
  IPC --> Ops
  Ops --> Runner
  Runner -->|spawn| GitCLI[(system / GIT_MANAGER_GIT_PATH)]
  IPC --> Store
  IPC --> Prov
  Prov -->|HTTPS| HostAPIs[(GitHub / GitLab / Bitbucket)]
  IPC --> Upd
  Upd -->|electron-updater| GHReleases[(GitHub Releases)]

Opening a repository lands on History. The graph uses most of the workspace; selecting a commit shows files and a Monaco diff, inline or side by side, with syntax colors for the file's language (the palette button turns them off).

Full write-up: docs/architecture.md.

MIT