GitKraken is a graphical Git client that displays repository history as a commit graph. It separates the working directory, staging area, commits, branches and remotes rather than treating every changed file as saved history. Uncommitted changes appear in a WIP node. Staging a file or hunk selects content for the next commit; it does not publish that content to a remote repository.
Undo, revert and amend change different history
GitKraken can stage selected files or individual hunks before a commit. This permits a focused commit even when one working file contains unrelated edits. It can also undo supported local Git actions while their effects remain local. Reverting a commit creates a new commit that applies the opposite changes. That preserves the existing published history and suits a commit that other people may already have pulled.
Amending replaces the selected commit content or message. When that commit already exists on a remote, the rewritten history requires a force push. The new commit identity can leave another contributor’s branch based on the old identity, so amend is not a cosmetic edit after publication.
Interactive rebase builds a commit plan
Interactive rebase works on commits after a chosen common ancestor. Pick keeps a commit, reword changes its message, squash combines it and drop removes it from the rewritten sequence. A rebase started inside GitKraken must finish there rather than moving midway to another Git client.
A conflict pauses that plan until the files receive a resolution and the rebase continues. The visual graph shows the rewritten result, but it cannot decide which competing line reflects the intended code. The output editor available during conflict work also depends on the product capability available to the account.
Merge choices do not all create a commit immediately
A branch can begin from a selected graph node. Pull and push exchange commits with a remote, while merge combines histories locally before a push. A squash merge stages the combined changes but leaves the resulting commit for the user to create manually. Seeing the files in the staging area therefore does not mean the branch already contains the final squash commit.
GitKraken profiles separate identities, service integrations, preferences and open tabs. Multiple-profile capability depends on the available product level. Choosing the wrong active identity can still attach an unintended author to a new commit even when the correct repository and branch are open.
Workspaces group repositories without merging them
A local workspace groups repositories found on one machine. A cloud workspace can synchronize its grouping through a hosting-service integration and can be shared. The repositories keep their own histories, remotes and working directories; placing them in one workspace does not create a monorepo or one combined Git transaction.
