GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing gitcomet.dev — GitComet features

Features

Every part of your Git workflow, together

GitComet is a desktop Git client written in Rust. It reads your repository directly with gitoxide, renders through the GPU, and keeps repository browsing and editing on your own machine. Fetch, pull and push use the remotes you configure.

Work from the change in front of you: right-click a commit to cherry-pick it, a branch to compare it, or selected diff lines to stage them. Files, stashes and worktrees have their own actions too.

Download GitComet View on GitHub

Review

Diffs you can actually read

Most of the time you spend in a Git client is spent reading changes. GitComet treats the diff as the main view rather than a preview pane.

Inline and side-by-side

Switch layouts with Alt+I and Alt+S, and step through the changed files with the arrow keys. Scroll sync can be vertical, horizontal, both, or off. Collapse to changed lines only when a file is mostly untouched.

Syntax highlighting

Syntax highlighting for programming, configuration and markup languages, in the diff and in the editor views.

More than plain text

Rendered Markdown with common HTML and offline Mermaid diagrams, side-by-side image and SVG diffs, and a minimap of the whole file. Search a diff with case, whole-word, and regular expression matching.

Side-by-side diff in GitComet with syntax highlighting and word-level change highlighting — Side-by-side diff with syntax and word-level highlighting.

Diffs You Can Actually Read

28 seconds

Review rendered Markdown, Mermaid diagrams, tables and image changes in GitComet. Compare before and after side by side, or switch back to source text when you need the exact edit.

Watch with the written walkthrough

Steps shown in the video

Open a changed Markdown document in the diff. Its preview renders the document, including tables and Mermaid diagrams.
Press Alt+S to compare the rendered before and after versions side by side.
Switch to source text to inspect the exact Markdown and diagram syntax that changed.
Open the changed SVG image to compare the two versions visually, side by side.

Staging

Commit exactly what you meant to

A commit is easier to review when it contains one idea. GitComet lets you split work apart without rewriting the file.

File, hunk, or single line

Keep a fix separate from the rest of your edits. Right-click a changed line or a selection to stage or unstage just those lines, or choose a whole hunk. The diff gutter works too; Space stages the current file and jumps to the next one.

Discard with care

Discard a single hunk instead of the whole file, amend the previous commit, and get a warning before staging a file that still contains conflict markers.

Ignore without leaving

Keep generated files out of your commits. Right-click an untracked file to add its exact name, folder or extension to .gitignore.

Stage Only What Matters

48 seconds

Turn several edits in one file into focused commits. Select and stage just the fix, discard a debug line, and edit a remaining typo directly in GitComet before committing the rest.

Watch with the written walkthrough

Steps shown in the video

Select the changed lines belonging to the fix in the diff and stage only those lines.
Discard the leftover debug line while keeping the other intended edits.
Write a message for the staged fix and press Ctrl+Enter to commit it on its own.
Press Alt+E to edit the remaining typo in place. Press Ctrl+S to save the file and return to the diff.
Press Space to stage the remaining change, then commit it separately. The history now contains two focused commits.

History

History that stays fast when the repository is not small

GitComet was started because existing clients stopped being usable on codebases the size of Chromium. History loads in pages and renders while the walk is still running.

Rendered commit graph

A lane graph drawn on a custom canvas, tuned for repositories with tens of thousands of commits. Choose which columns you want and highlight the selected commit's chain.

Filter down to the change you want

Search across the whole history by commit summary, author or SHA prefix, with case, whole-word and regex options. Focus on selected branches or remotes, hide remotes from the graph, and filter by author or file. Tool and bookkeeping refs are hidden by default, with controls in Settings. See how to filter history.

Compare anything

Right-click a commit, branch or tag to compare it with your working tree, or mark it for comparison with another revision. The working-tree comparison updates as you edit. Browse the whole repository as it was at any commit.

Travel Through Your History

44 seconds

Choose a history view, revert a mistaken merge while preserving history, and create a hotfix branch from an earlier release. GitComet also shows another worktree’s changes directly in the log.

Watch with the written walkthrough

Steps shown in the video

Change the history mode to First-parent to follow the mainline, Merges only to inspect merges, or All branches to see the wider graph.
Select the mistaken merge and press R to revert it. Choose the parent belonging to main as the mainline to keep.
Confirm the revert. GitComet creates a new commit undoing the merge’s changes while keeping the earlier history intact.
Right-click a commit from an earlier release and choose Create branch from this commit. Name the hotfix branch and check it out.
Select another worktree’s changes in the log to inspect its work in progress without switching tabs.

Rewriting

Clean up a branch without writing a rebase todo by hand

History rewriting is where a GUI earns its place: the operations are easy to describe and easy to get wrong in a terminal.

Interactive rebase

Start an interactive rebase from a commit's right-click menu. Drag commits to reorder them, then pick, reword, squash, fixup, or drop. Autosquash groups fixup! and squash! commits the same way Git does.

Edit a commit message

Click the pencil in commit details to edit its message, then choose Update commit. GitComet asks for confirmation when the commit is already on the upstream. Learn how to edit a commit message and when rewriting is available.

Cherry-pick and squash

Bring one change onto your current branch without merging the whole branch: right-click its commit and choose Cherry-pick. Select multiple commits for an interactive cherry-pick, or squash a contiguous range with a live message preview.

Get back out again

Reset soft, mixed, or hard, and abort an in-progress merge, rebase, or cherry-pick. GitComet shows which sequencer state the repository is in.

Pick the Fix, Leave the Rest

43 seconds

Bring one fix from a feature branch onto main without merging the rest of the branch. Then squash two unpushed commits into a single commit before pushing.

Watch with the written walkthrough

Steps shown in the video

Mark main for comparison, then compare the feature branch with it to identify the fix you need.
With main checked out, right-click the fix commit and choose Cherry-pick. Only that commit’s changes come onto main.
Review the new commit and the other unpushed commit on main.
Shift-select the two commits, open their actions menu and choose Squash 2 commits.
Review the combined message and complete the squash. The selected changes are now one commit, ready to push.

Rewrite History, Cleanly

38 seconds

Clean up a branch with GitComet’s interactive rebase editor. Fold fixup commits into their targets, reorder the remaining commits and replace an unclear commit message before completing the rebase.

Watch with the written walkthrough

Steps shown in the video

Open an interactive rebase for the feature branch from the commit actions menu.
Use autosquash to fold fixup commits into the commits they amend. Review the resulting sequence in the editor.
Drag commits into the order you want them to appear in the branch history.
Choose Reword for the vague commit message and continue the rebase. Enter a descriptive message when prompted and save it.
Review the completed branch history to confirm that the commits are ordered and named as intended.

Repository

The rest of Git, not just the parts that are easy to draw

Branches, remotes, and tags

Compare a branch before bringing it into your work. Right-click it in the sidebar to compare, merge, squash or rebase. Manage upstreams and remote URLs, prune merged branches, and create lightweight or annotated tags.

Worktrees and submodules

Open a branch straight into a new worktree from its context menu. Removing a worktree keeps its branch unless you choose to delete it. Submodules show a diff summary and inline diffs, and any submodule command asks for trust before it runs. See the linked worktree guide.

Stashes and patches

Set unfinished work aside, with or without untracked files. Right-click a saved stash to apply, pop or drop it. Export a commit as a patch file, or apply one to the index or the working tree.

Push and pull the way you want

Pull as merge, rebase, fast-forward only, or fast-forward if possible. Force push with lease, and see how far ahead or behind the upstream you are.

Commit, amend and skip hooks

Commit or Commit & Push from the message box, tick Amend to replace the last commit, or tick Skip hooks to leave out pre-commit, commit-msg and pre-push for one window. Git LFS content is still uploaded before the push. Read about amending and skipping hooks.

Automatic fetch

Enable background fetching in Settings → Remotes to keep open repositories current. Tab badges show incoming commits; the Pull menu shows fetch status. You decide when to integrate the changes. See automatic fetch settings and status.

Bare repositories

Browse committed files and history, fetch and push, and manage linked worktrees in a bare repository. The Git Bare badge explains which actions need a working tree. Read about bare repository support and conversion.

Clone with progress you can cancel

Cloning reports live progress and can be aborted. Credential, SSH passphrase, and host-verification prompts appear in the app instead of a hidden terminal.

Git LFS and git-annex

See large-file status and content in diffs. Download, track and lock LFS files, or get, copy and move annexed content between repositories and special remotes. Install git-lfs or git-annex to use their commands. See the LFS guide and git-annex guide.

Blame that reads like history

Annotate any file at any revision. Lines are shaded by recency, uncommitted lines are marked as staged or unstaged, and any line jumps to the commit that introduced it.

Don’t Miss What’s New, Fetch Automatically

46 seconds

Turn on automatic fetch and GitComet fetches every open repository in the background, so new commits show up on each tab. GitComet 0.3.3 also lets you fix an older commit message, hide a remote, focus history on a branch and open a branch in a worktree.

Watch with the written walkthrough

Steps shown in the video

Press Ctrl+, to open Settings, select Remotes and turn on Automatically fetch repositories. Set how many minutes to wait between fetches.
GitComet fetches every open repository in the background without pulling. Each repository tab shows its number of incoming commits, and the sidebar shows how far main is behind and ahead.
Select a commit three commits back and click the pencil in Commit details. Fix the typo in its message and press Ctrl+Enter to update the commit.
Right-click a remote in the sidebar and choose Hide from history graph. Its branches no longer appear in the history.
Right-click a branch and choose Focus to show only its history. Stop focus returns to the full graph.
Right-click a branch and choose Open in new worktree, then press Enter to add it. For a branch already checked out in a worktree, choose Open worktree to jump straight to its tab.

Borrow Changes, Commit Later

32 seconds

Apply selected files from another branch without bringing over its commits. GitComet stages the chosen changes on your current branch so you can review them before creating a commit.

Watch with the written walkthrough

Steps shown in the video

With main checked out, compare the feature branch with main to see which files differ.
Ctrl-click the changed files you want to bring over, leaving the other files unselected.
Choose Apply changes. When asked whether to commit the applied changes, choose No.
Return to the working tree. The selected changes are staged on main, and no new commit has been created.
Review the staged diff, adjust the changes if needed and commit when you are ready.

GitComet blame view with recency heat colouring on each line — Blame, shaded by how recently each line changed.

Workflow

Fewer reasons to leave the window

Edit files in place

A built-in editor with syntax highlighting and optional autosave. Press Alt+E, fix the typo you just spotted in the diff, save, and stage it.

Embedded terminal

A real shell inside the panel for the commands no GUI should try to replace. Your external terminal and code editor are one shortcut away when you prefer them.

Command palette

Ctrl+P reaches close to 50 commands by name. Global back and forward navigation, repository tabs, pinned and recent repositories, and session restore on launch.

Keyboard first

Fetch, push, pull, stage all, switch branch or toggle the sidebar and terminal without the mouse, and move between the graph, file list and diff with F6. Press Ctrl+/ for a cheat sheet of every shortcut. See the keyboard shortcut reference.

Workspaces and windows

Group repositories into saved workspaces, move repository tabs between windows, and give each workspace its own theme. Repository preferences stay in sync across linked worktrees.

Files and documents

Right-click a file or folder in the Files sidebar to rename, copy or move it, with clipboard support and Undo/Redo. Create files in place, open recent documents and edit files outside a repository from the Documents button.

Keep Your Hands on the Keyboard

46 seconds

Review a commit, stage your work block by block and push it without reaching for the mouse in GitComet 0.3.4. Find shortcuts by action or key in the searchable cheat sheet, discard a leftover debug line and commit and push in one go.

Watch with the written walkthrough

Steps shown in the video

Press Ctrl+/ to open the keyboard shortcut cheat sheet. Search by action or by key, then press Esc to close it.
Select a commit in the graph and press Enter to open its files. Press Enter again to open the diff, then use Down to step through the changes.
Press Esc to step back to the graph. Press Up to select Uncommitted changes, then Enter to open your working changes.
Press S to stage the outlined change block. Move through the remaining blocks and stage the changes you want to commit.
Press U to discard the leftover debug line. The next file opens automatically; discard its unwanted change too.
Write a commit message and press Ctrl+Shift+Enter to commit and push in one go. Return to the graph to see the commit in sync with origin.

Worktrees, Files and Branches

31 seconds

Inspect another worktree’s uncommitted changes from the log, duplicate and rename a file in the sidebar, then create and check out a branch without leaving GitComet.

Watch with the written walkthrough

Steps shown in the video

Select Worktree changes in the log to inspect the uncommitted files in a linked worktree without opening another tab.
Use Alt+Down to step through the changes in the diff.
Open the Files sidebar, select a file and press Ctrl+D to duplicate it. Rename the copy in place.
Press Ctrl+P to open the command palette and choose the command to create a branch.
Enter the new branch name with Checkout selected, then press Enter to create the branch and switch to it.

Two GitComet workspace windows, Orbit Studio and Design Library, using different themes — Two saved workspaces, each with its own window and theme.

Customization

Make it look and behave the way you want

Themes, including your own

31 built-in themes, plus an automatic mode that follows your operating system and switches live. Choose a theme in Settings → Appearance or override it per workspace. Add custom themes as JSON bundles. See the theme guide.

Typography and scale

Pick your interface font and your editor font separately from the fonts installed on your system, toggle ligatures, and scale the whole interface without touching your display settings.

Links back to your forge

Copy a permalink to a commit or a file for GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, Codeberg, Forgejo, and AWS CodeCommit. Commit hashes and URLs inside commit messages are clickable.

Make It Yours

29 seconds

Adjust text size, switch between GitComet’s built-in themes and open another workspace with its own appearance. Theme changes appear immediately as you work.

Watch with the written walkthrough

Steps shown in the video

Press Ctrl+, to open Settings and select Appearance.
Adjust the interface text size to make the application comfortable to read.
Choose from the 31 built-in themes shown in this recording. The application updates as you select a theme.
Press Ctrl+Shift+R to open the repository and workspace switcher, then choose another workspace.
Notice that each workspace keeps its own theme, making the two work contexts easier to distinguish.

GitComet in the built-in GitComet Dark theme, showing the branch sidebar, commit graph, and history — The same view in four built-in themes: GitComet Dark, GitComet Light, Tokyo Night and Sunset Veil. Any of them expands to full size.

The same GitComet view in the built-in GitComet Light theme — The same view in four built-in themes: GitComet Dark, GitComet Light, Tokyo Night and Sunset Veil. Any of them expands to full size.

Platform

Native on all three, including ARM

Windows

A signed MSI installer and a portable build, on x86-64 and ARM64. Also on the Microsoft Store.

macOS

A notarized disk image on Apple silicon and Intel, or brew install --cask gitcomet.

Linux

apt, AUR, Gentoo GURU, Nixpkgs, Homebrew, AppImage, .deb and Fedora RPM packages, on x86-64 and ARM64. Wayland with an automatic X11 fallback, and WSLg.

GitComet needs a local Git installation of 2.53 or newer. It is licensed under the AGPL-3.0, and the workspace forbids unsafe Rust code outright.

Try it on your largest repository.

That is the one that tells you whether a Git client is worth keeping.

Download GitComet See the merge tool View on GitHub

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.