Shouldn't the change be made immutable after bookmark set and push?

[xoich]

I see now that only

I found a surprising behavior.

I have added a few changes to the develop bookmark, then I want to push these to git. So I do jj bookmark set develop and jj git push.

What happens: develop@origin is set in the current change and is mutable
What I expect instead: develop@origin is set to the current change, it is made immutable and so a new change is added on top of it.

Is the behavior normal?

This has now caused me many time troubles when I started modifying the working copy and so adding a new hidden commit on the develop@origin change.

[xoich]

I see now that only the trunk() branch is immutable. It's a bit of a confusing default when more than one branch is used for shared development in a team. But I'm not sure how it could be done differently.

[bnjmnt4n]

You can customize the set of immutable commits: https://jj-vcs.github.io/jj/latest/config/#set-of-immutable-commits. This can be done on a per-repo basis as well, so you could mark different bookmarks (branches) as immutable based on the repo's practices.