A new visual tutorial walks through a full Jujutsu jj session, from the first edit to an undo, and shows where the tool departs from Git. The tutorial follows one small timer app through 23 steps. Everything the author does ends up as an ordinary Git branch for teammates.
Jujutsu, usually called jj, stores its history in a Git repository, so adopting it doesn’t require teammates to change anything.
How Jujutsu jj treats the working copy
The first idea is that the working copy in jj is a real commit, labeled @, rather than a staging area off to the side. When you change files, such as app.js and style.css, no add or staging step exists. Whatever jj command you run next records the files directly into @.
The message can be written whenever you like, whether before the work, once it’s finished, or several rewrites down the line. The tutorial uses `jj describe -m “Add pause button”` to name the change once the work is done.
Two IDs for each commit
Every commit carries two identifiers. The change ID uses letters, identifies the unit of work, and stays fixed. The commit ID, written in hex, names one exact snapshot, so each rewrite gets a new one. `jj evolog` lists the earlier snapshots of one change, and nothing is overwritten.
Starting new work is `jj new`, which begins an empty change on top. The change below isn’t locked. To go back and fix a bug in the pause button, `jj edit mz` moves @ there, with no stash and no detached state to manage. The change above it follows along automatically: jj rebases it, giving it a new commit ID but keeping the same change ID.
Moving work between commits
Spot a typo in the README that belongs in an earlier change? Make the edit where you are, then run `jj squash` to move it into the parent. The opposite move is `jj split`, and `jj squash –into` can target any commit.
Conflicts that can wait
Git stops a rebase when it hits a conflict. In jj the rebase finishes, and the conflict is stored inside the commit, marked in red. Every commit above it carries the conflict until someone fixes it. In the tutorial, a teammate pushes to main, `jj git fetch` pulls it in, and moving the stack onto the new main produces two commits labeled (conflict).
Nothing blocks you. When you’re ready, `jj new mz` starts a change on top of the first conflicted commit, and you resolve it there.
Parallel lines of work are simple too. Starting from main with a new change called “Try a dark theme” opens a second line with no branch name. `jj log` shows both lines together and `jj edit` or `jj new` hops between them, so there’s no active branch to switch away from.
Bookmarks instead of branches
A Git remote expects a branch name when you push. jj supplies bookmarks, simple labels attached to a commit. Adding commits above doesn’t drag a bookmark upward, yet it tracks its own commit through every rewrite. The tutorial runs `jj bookmark set pause-button -r pn` and then `jj git push –bookmark pause-button`. Teammates see a normal Git branch and never need to know jj was involved.
Nothing is lost
Each command is recorded as an operation, and `jj op log` lists them all. Each entry captures the complete repository state right after that command. That is what makes the last step possible. In the tutorial, the author abandons the dark theme commit with `jj abandon @` and then regrets it. `jj undo` rolls the repository back a single operation, and the dark theme reappears unchanged.
How it compares for Git users
Several Git habits carry over to Jujutsu jj. The history is still Git commits, the remote is still a Git remote, and the push is still a branch. The differences are in the daily loop:
- No staging area, because the working copy is a commit.
- Stable change IDs that survive rewrites.
- Rebases that complete even when they conflict.
- An operation log that makes undo reliable.
What to try next
For teams curious about Jujutsu jj, the low-risk path is to use it alone on a Git repository, since the rest of the team won’t notice. The tutorial’s 23 steps give a clear map of the commands to learn first, starting with `jj log`, `jj describe`, `jj new`, `jj squash` and `jj undo`.
Source: brajeshwar.com