You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you expect to be the first with that revset?
I considered adding first() or limit() before, but rejected my idea because the order of revsets seemed to be implementation detail in jj, and the visible order could also be affected by #242.
It might be better to specify the sorting order explicitly (e.g. latest() to pick the first element in committer-timestamp order.)
Makes sense, first was just the first singularizing function I could think of 😅 -- latest(...) might be even better for the rebase workflow I was thinking of (more often than not, I would probably be okay with just rebasing the latest commit I'm working on, leaving any older ones untouched).
Also, I just realized, the rebase example in my first comment should probably be more like the one below (exclude main: so that the command is repeatable) --
$ jj rebase -b 'latest(remote_branches("", origin).. ~ (main: | empty()))' -d main
This could be useful with commands like rebase that only take a single revision -- for example,
The text was updated successfully, but these errors were encountered: