Jj First Time

In Jujutsu a bookmark is a named pointer to a commit, like a Git branch, but unlike a Git branch it does not move forward by itself when you commit¹. jj git push only pushes bookmarks that are tracked and that are ahead of their remote counterpart. So after

jj commit -m "some work"

the local master bookmark still points at the previous commit, and a plain jj git push reports:

Warning: No bookmarks/tags found in the default push revset:
remote_bookmarks(remote=origin)..@

The usual fix is to move the bookmark by hand every time:

jj bookmark advance master    # or: jj bookmark set master -r @-
jj git push

For a simple single-bookmark repository like this one, the experimental "advance branches" feature can move the bookmark for us². The repo-local configuration is:

[experimental-advance-branches]
enabled-branches = ["master"]
disabled-branches = []

set with:

jj config set --repo experimental-advance-branches.enabled-branches '["master"]'
jj config set --repo experimental-advance-branches.disabled-branches '[]'

Now jj commit advances master to the commit it just created, and a plain jj git push pushes it.

The feature only advances a bookmark that already points at the working copy's parent (@-)³; it will not skip a bookmark forward from an older commit. So when adopting this, align master with the tip once:

jj bookmark set master -r @-

After that every new commit keeps it there. (This was needed here because master was still three commits behind.)

The bookmark must also be tracked. When a workspace is cloned or initialised this is normally automatic for the default branch; otherwise:

jj bookmark track master@origin

jj st                 # status of the working-copy commit
jj diff               # what changed
jj log                # history / bookmark position
jj commit -m "..."    # describe @ and start a new empty @ on top
jj git push           # push master (tracked) to origin
jj git fetch          # update remote bookmarks

The working copy is itself a commit. Edits are snapshotted automatically, so there is no staging area.

• experimental-advance-branches.enabled-branches is experimental. It advances every matching bookmark that is an ancestor of the new commit, which is fine while master is the only bookmark here. If more bookmarks appear, list them explicitly or fall back to jj bookmark advance⁴.
• Jujutsu refuses to push commits with an empty description. Describe them, squash them, or pass --allow-empty-description.
• The configuration lives in ~/.config/jj/repos/<id>/config.toml (repo scope), so it is per working copy, not committed to Git.