trunk() pointing to multiple commits

[whatisaphone]

I have a problem that would be solved by pointing trunk() to multiple bookmarks. I tried this and it worked, despite the docs saying:

• trunk(): You can override this as appropriate. If you do, make sure it always resolves to exactly one commit.

What's the reason behind that sentence? What might break if I keep this config?

[jennings]

I think it's probably fine, although others might get confused if trunk() resolves to multiple revisions. If you borrow a revset expression from someone, you might have to adapt it.

As far as I can tell, jj doesn't use trunk() for anything except in the definition of immutable_heads(), and that definition would tolerate multiple revisions.

[emilazy]

jj rebase -d 'trunk()' is a somewhat common thing it will likely break. Of course if you specify the bookmark explicitly that won’t be an issue.