FR: jj log should indicate when hidden remote bookmarks exist?

[neongreen]

A coworker had a local bookmark foo and a remote branch foo@origin. The bookmark wasn’t tracking the remote branch, because they didn’t know about jj bookmark track.

The commit corresponding to foo@origin was showing up as immutable. I suppose it was because of a remote bookmark pointing to it? but I didn’t realize the remote bookmark even existed.

Three solutions come to mind:

• jj show for immutable commits could always mention why exactly they are immutable. This seems tricky if the user redefines immutable_heads.
• Or jj log could somehow indicate that remote bookmarks exist, even if untracked.
• Or there should be a warning when an untracked remote bookmark with the same name as local bookmark exists?

FWIW I’m not 100% sure my recollection is accurate. If it turns out jj log does show untracked remote bookmarks, I’ve no idea what went wrong

[yuja]

The default jj log output hides immutable revisions as "uninteresting". If untracked remote bookmarks should be included in jj log (or they should be considered mutable), the user will have to configure either revsets.log or revset-aliases.'immutable_heads()'.

https://jj-vcs.github.io/jj/latest/config/#log

I have no idea how this could be presented to new users. It would be too verbose if jj log/show printed things which are intentionally excluded from the output.