Appearance
Git Log and Git View
The right sidebar's Git tab has a Changes | Log toggle. Changes is the working-tree panel described in Git Changes Panel. Log shows the commit history of the active project with a commit graph. A full-window Git view adds a branch tree and a wider layout. Both are free on every plan and need no flag.
They need the native desktop or mobile app and a project that is a git repository. In the web build they show a notice instead, the same as the Changes tab.
The Log
Each row shows the commit graph (lanes, merges and the branch, tag and HEAD badges), the subject, the author and the date. The list loads more commits as you scroll.
- Click a commit to open its details: the full message, author, committer, parent links and the changed files. Each file expands to the patch that commit made. Click a parent link to jump to that commit.
- Keyboard: the arrow keys move between commits, Left goes to the child commit and Right goes to the parent.
- Open in the Git view in the sidebar Log opens the full view for the same project.
Search and filters
- Text matches commit messages. Typing a hash of 4 or more hex digits looks up that commit and shows it.
- Branch or tag limits the log to one ref.
- Author and Date range (last 24 hours, 7 days, 30 days or year).
- Paths takes a comma-separated list and shows commits that touched them.
In a narrow sidebar or on a phone, author, date and paths fold behind a Filters toggle. The graph is hidden while a text, author or date filter cuts the history, because the lanes would no longer connect.
Commit actions
Right-click a commit, long-press it on touch, or use the ... button in the details. The menu has:
- Copy revision number and Copy as patch
- Cherry-pick
- Checkout revision
- Reset current branch to here with Soft, Mixed or Hard. Hard asks you to confirm.
- Revert
- Undo commit (the HEAD commit only; keeps its changes staged)
- Edit commit message (the HEAD commit only)
- New branch and New tag
- Rebase current branch onto commit
- Go to parent and Go to child
- View in browser for GitHub, GitLab, Bitbucket and Azure DevOps remotes
When a merge, rebase, cherry-pick or revert stops on a conflict, a banner appears with Abort to cancel the operation. Resolve the files in a terminal or the editor and continue there.
The Git view
Open it from Open in the Git view in the sidebar Log, from Git in the main navigation (route /git), or press F1 and run Go to Git. Pick the project at the top. On wide windows it has three columns: the branch tree, the log and the commit details. On narrow windows the columns stack.
Branch tree
The tree has Local, Remote and Tags groups. Names split on / into folders. A search box filters the tree, each branch shows its ahead and behind counts, and the current branch is starred.
The branch menu has:
- Checkout (double-click does the same)
- Checkout as local branch for a remote branch
- New branch from
- Merge into current
- Rebase current onto
- Fetch for a remote
- Rename
- Delete, which asks to confirm and asks again before force-deleting a branch that is not merged
- Delete tag
- Show in log
The toolbar has Fetch all remotes and Refresh.
Where commands run
Every operation runs as the project's run-as user on the project's node, so your ~/.gitconfig, credentials and hooks apply. This also holds for projects on other cluster nodes. Fetch and rebase never prompt, so a remote that needs an interactive password or passphrase fails with its error instead of hanging.
Limitations
- Undo commit and Edit commit message only work on the HEAD commit.
- Commits made in a terminal show up on the next window focus or Refresh, because the project file watcher skips
.git. - Conflict resolution happens outside the Log: use the banner's Abort, or finish the operation in a terminal.