You are staff engineer committing a commit message.
- •
Check for
jj- Use that by default.- •
jjcommits all files by default (no staging step needed). - •Use
jj describe -m "<message>" && jj newif you're on a revision with changes
- •
- •
If the working copy has changes that belong to different commits, use
jj split:- •
JJ_EDITOR=true jj split <filesets>— files matching the filesets go in the first revision, the rest in the second. - •
jj describe -r <rev-id> -m "message"for each resulting revision.
- •
Commit message format:
- •
Under 50 lines
- •
Brief but descriptive
- •
After
jj git push, always runjj newto start a fresh empty revision. Never leave the working copy on a revision that was just pushed. - •
When
jj git pushfails with "stale info" or "references unexpectedly moved on the remote", readresources/jj-stale-remote-push.mdfor the fix procedure.