Using Jujutsu (jj) VCS
This guide provides the definitive instruction set for working with Jujutsu (jj).
Core VCS Commands
CRITICAL: This repository uses Jujutsu (jj), not git. Always use jj commands for version control operations.
- Check status:
jj st --no-pager - View history:
jj log --no-pager - Create commit:
jj commit -m "message" - Only commit related changes:
jj commit -m "message" <filesets>- Example:
jj commit -m "fix auth bug" src/auth.rs tests/auth_test.rs - NEVER use
jj restoreto exclude files from a commit; use fileset commits instead.
- Example:
- Push:
jj git push - Push main:
jj bookmark set main -r @- && jj git push - Undo last jj command:
jj undo - Help:
jj help-- use this is you need to research howjjworks. Or use available MCPs.
Before Any Commit
Run this safety checklist before jj commit:
- Run
jj st --no-pager. - Commit with
jj commit -m "message"(or fileset form when committing only related paths).
If location is ambiguous (for example, multiple checkouts/workspaces), confirm with jj root.
Search and History Operations
History Search
- Use
jj log -r '<revset>'with appropriate revset expressions - For searching by message:
jj log -r "description(pattern)" - For searching by author:
jj log -r "author(pattern)" - For date-based searches:
jj log -r "after(date)"orjj log -r "before(date)"
Code Search
- Prefer
rg(ripgrep) orgrepover any VCS-integrated grep - Do not use
git grepin jj repos; userginstead
Working with Revisions (Revsets)
@— Current working-copy parent revision@-— Parent of current revision<ref>— Specific revision by ref (supports short hashes)main— Branch by nameancestors(@)— All ancestors of current revisiondescendants(@)— All descendants of current revision
Important Constraints
- Never use
gitcommands in.jj/repositories—translate to jj equivalent. - Do not mix
gitandjjoperations; they have incompatible internal models. - If a jj command fails, provide the error message and suggest alternatives.
Integration with Search and Analysis
- Use
jj loginstead ofgit logto find recent changes. - Use
jj diffto compare revisions. - Never use
git log -Sorgit log -G; translate tojj logwith appropriate revsets.