Working with Commits
Cherry-pick (including series), revert, reset, uncommit, patches, compares, and file tree
Right-click a commit in the graph for the context menu. Everyday actions sit at the root; rarer ones live under More. Every action maps to a normal git command.
Root menu
| Action | What it does |
|---|---|
New Branch from 'sha'… (Ctrl+Shift+B) | git branch <name> <sha> |
New Tag at 'sha'… (Ctrl+Shift+T) | Lightweight tag on the commit. |
| Merge 'sha' into '<branch>' | Merges into the current branch. |
| Rebase '<branch>' to Here… | Moves your branch onto the commit. |
| Cherry-pick this commit | Applies the commit on top of HEAD. For merge commits GitBor uses mainline ^1. |
| Revert this commit | Creates a new commit that undoes this one (mainline ^1 for merges). |
| Uncommit to staging | Only on HEAD, and only if not yet pushed: soft-reset to the parent; changes stay staged. |
| Reset '<branch>' to Here | Soft / Mixed / Hard — see below. |
| Checkout Commit… | Detaches HEAD at this commit. |
Copy SHA (Ctrl+C) | Full hash. |
“More” submenu
| Action | What it does |
|---|---|
| New Annotated Tag… | Name + message (git tag -a). |
| Interactively Rebase '<branch>' to Here… | Opens the interactive rebase editor. |
| Save as Patch… | Saves the commit as a .patch file. |
| Compare to Local Changes | Diff of the selected commit against the current working tree. |
Copy Commit Info (Ctrl+Shift+C) | Short hash, subject, author, and date in one block. |
Multi cherry-pick
- Select several commits in the graph: Ctrl+click (toggle) or Shift+click (range). Or search with Ctrl+F and click Select all.
- Right-click any selected commit → Cherry-pick N commits.
- Commits apply oldest → newest via the git sequencer.
- On conflict, a top banner offers Continue / Skip / Abort — same pattern as rebase. Resolve in the Merge Editor, then continue.
Cherry-pick this commit remains when only one commit is selected.
Reset
| Mode | Effect |
|---|---|
| Soft | Moves the branch tip; changes stay staged. |
| Mixed | Moves the tip; changes stay in the working tree (unstaged). |
| Hard | Moves the tip and discards uncommitted changes. Asks for confirmation — undo only via reflog. |
Commit details panel
Clicking a commit opens tabs on the right:
| Tab | Contents |
|---|---|
| Commit | Author, date, message, Explain commit (AI). |
| Changes | Changed files; click opens the diff. |
| File Tree | Full repository tree at that revision (git ls-tree), not only the diff. Click a file to see contents at that revision; context menu has Blame / File History. |
Conventional Commits
When the repo uses Conventional Commits, a type selector (feat, fix, docs…) appears left of Subject to insert a valid prefix when the subject fails the format check.
Explain with AI
Explain commit on the Commit tab gives a short high-level summary. See AI Helpers.
Safety
History-rewriting ops record HEAD first (recover via Reflog). Uncommitted changes are auto-stashed when the operation would otherwise lose them. See Data Protection.