zlacker

[parent] [thread] 5 comments
1. arccy+(OP)[view] [source] 2025-12-05 12:14:52
note that bookmarks don't float, unlike git branches, so if your pattern is to produce a lot of commits, you'll want something to keep your jj bookmarks pointing to the top of your pile of commits.

this is less of a problem if you're more into the 1 change == 1 commit workflow.

replies(2): >>lima+f >>pimeys+u
2. lima+f[view] [source] 2025-12-05 12:16:49
>>arccy+(OP)
There's an experimental-advance-branches feature which helps with that!
3. pimeys+u[view] [source] 2025-12-05 12:18:05
>>arccy+(OP)
There's a very common alias `jj tug` for this case:

  tug = ["bookmark", "move", "--from", "heads(::@- & bookmarks())", "--to", "@-"]
It moves the nearest bookmark to the commit before the current one (which should be your working commit).
replies(2): >>stavro+U4 >>mhitza+Zz
◧◩
4. stavro+U4[view] [source] [discussion] 2025-12-05 12:47:48
>>pimeys+u
Thanks, I replaced my Frankenstein's monster of a parsing pipeline with this, very useful!
◧◩
5. mhitza+Zz[view] [source] [discussion] 2025-12-05 15:23:52
>>pimeys+u
This looks like any other git arcane incantation. If this is a common pattern and jj aims to make things easier, should probably be part of the core commands, no?
replies(1): >>stevek+762
◧◩◪
6. stevek+762[view] [source] [discussion] 2025-12-05 22:37:51
>>mhitza+Zz
It's something that makes a specific workflow easier, a lot of folks that use jj don't necessarily use that workflow.

That doesn't mean it couldn't be a core command someday, but given that the alias works well for people, there's not a ton of reason to make a whole new command. You configure the alias and you're off to the races.

[go to top]