jj-bookmark

Create a new bookmark at the given revision

$ jj [[b|bookmark]] [[c|create]] [[-r|--revision]] [revision] [name]

$ jj [[b|bookmark]] [[l|list]]

$ jj [[b|bookmark]] [[m|move]] [[-t|--to]] [revision] [name]

$ jj [[b|bookmark]] [[t|track]] [name]@[remote]

$ jj [[b|bookmark]] [[d|delete]] [name]

$ jj [[b|bookmark]] [[f|forget]] [name]

jj bookmark [OPTIONS] [BOOKMARKS]...

-d, --delete
    Delete the specified bookmarks instead of moving them (mutually exclusive with tracking)

-D, --delete-all
    Delete all bookmarks

-r, --at-rev <REV>
    Move bookmarks to this revision instead of working-copy commit

-R, --remote <REMOTE>
    Operate on remote bookmarks from the given remote (list/track/delete)

--track <REV>
    Make bookmark track changes to the given revision (mutually exclusive with --delete)

The jj bookmark command is part of Jujutsu (jj), a Git-compatible version control system designed for better usability and performance. Bookmarks in jj are mutable named pointers to commits, similar to Git branches but with key differences: they can point to multiple commits via "conflict commits" and are advanced explicitly rather than via implicit tracking.

Without arguments, jj bookmark lists all bookmarks in a concise table showing name, status (e.g., diverged, moved), and commit ID. Providing bookmark names moves them to the current working-copy commit (or specified revision). Multiple bookmarks can be advanced together, with the last argument treated as the target revision if it's a revset.

Common uses include creating (jj bookmark create name, though create is via moving from @), advancing during development, deleting unneeded ones, and managing remote bookmarks. Unlike Git, jj encourages explicit bookmark operations, avoiding automatic branch creation. This promotes clearer history and easier collaboration.

Bookmarks support tracking specific revisions and remote syncing, making it powerful for polyglot workflows.

Bookmarks are local by default; use git-push/git-fetch or jj git push/fetch for remotes. Moving bookmarks doesn't create merge commits. Conflicts in bookmarks result in "bookmark conflicts" resolvable via jj resolve.

jj bookmark # List bookmarks
jj bookmark main # Advance 'main' to working copy
jj bookmark -d feature # Delete 'feature'
jj bookmark foo bar @- # Move 'foo' to 'bar', advance 'bar' to parent of working copy