Commit Graph
Navigate repository history, search (including AI), compare commits and verify signatures
The commit graph is GitBor's main screen — the full repository history drawn with colored lanes for branches.
Performance
The graph is built for large repositories: histories with tens of thousands of commits scroll smoothly, and the computed layout is cached per tab, so switching tabs never recomputes it. The first open of a large repo can take a few seconds while the history loads; later opens are instant. History loads incrementally — a Load more commits control appears at the bottom when there's more to fetch.
Branch colors
Each branch gets a colored lane, and the color stays stable for the lifetime of the branch. Commits that were fetched from a remote but aren't in any local branch yet are marked with a hint so you can tell them apart from your local work.
Navigation
| Action | Result |
|---|---|
| Click a commit | Opens commit details and selects the diff of the first changed file. |
| ↑ / ↓ | Move between commits with auto-scroll, keeping the selection visible. |
| Enter | Open the details of the selected commit. |
| Double-click a branch (sidebar) | Checks it out. For a remote branch, GitBor offers to create a tracking local branch first. |
| Right-click a commit | Context menu with branch/tag, merge, rebase, reset, cherry-pick, revert, compare and copy actions — see Working with Commits. |
| Ctrl+F | Search the graph (see below). |
Branches in the sidebar have hover-actions (Pin / Solo / Hide / Note) that change what the graph shows — see Branches & Tags Sidebar.
Search
Press Ctrl+F to filter the graph by commit subject, author name, or hash prefix.
Toggle the AI switch in the search box (or prefix a query with ai:) for semantic search: GitBor sends a recent slice of history to your configured AI model and asks it to pick commits that match by meaning rather than by exact substring. This is a first, non-indexed version — it only sees the most recent commits. Details and limitations: AI Helpers.
Compare two commits
- Right-click the first commit → Compare From Here.
- Right-click the second commit → Compare with 'abc1234'.
GitBor shows the combined diff between those two points — handy for reviewing a series of changes or someone else's branch. You can also right-click a commit and choose Compare to Local Changes or Compare with Previous.
Signed commits
GitBor verifies GPG and SSH signatures and shows a badge next to each signed commit:
- Signed / valid — the signature is valid and the key is trusted.
- Untrusted / Expired — the signature is valid, but the key isn't trusted or has expired.
- Bad / Revoked — the signature is invalid or the key was revoked.
The badge reflects exactly what git reports for that commit's signature, so a "bad" badge means the same thing it would on the command line.