draft: add bump command to advance bookmarks to latest descandants

[obayemi]

The only thing I don't particularly like about jj is how I need to remember my branches names and type them (at least partially with completion) when I'm putting several changes on a branch (like during a review)

This PR adds a jj bookmark bump (or jj b b) that takes the latest bookmark in the changes tree and bumps it to the latest non-empty commit, removing IMO some of the pain of working with branches on environments where rewriting history is frowned upon by:

• removing the need to re-specify the branch name everytime you need to bump to commit
• having to think about if it is a simple jj b s <bookmark> or a jj b s <bookmark> -r @- if it was commited before instead of only updating the description

While staying a conscious effort

I was building this as a standalone script, but decided to integrate it directly to jj instead.

I'm probably going to use and maybe maintain this fork myself, please tell me if it is a feature you might consider integrating into upstream jj, and if so, what I could do to improve the code quality and integration with the rest of the codebase

Thanks in advance :)

DISCLAIMER: I'm not very familiar with jj's codebase and relied heavily on claude code to build this feature

Checklist

If applicable:

• I have updated CHANGELOG.md
• I have updated the documentation (README.md, docs/, demos/)
• I have updated the config schema (cli/src/config-schema.json)
• I have added/updated tests to cover my changes

[martinvonz]

See https://jj-vcs.github.io/jj/latest/contributing/ (things I've noticed after a quick look: squash the commits, update the commit description's subject line, move much of the PR description into the commit description)

[martinvonz]

And thanks for the PR, btw! I didn't mean to sound ungrateful.

[obayemi]

you're completely right sorry, I meant to keep the PR for myself while adding finishing touches and squash before opening it on the upstream repo but didn't check the target branch, I'll squash right away

[github-actions]

The following commits do not follow our format for subject lines:

• 1e66b45: Merge branch 'jj-vcs:main' into feat/jj-bump-version-management

Commits should have a subject line following the format <topic>: <description>. Please review the commit guidelines for more information.

All commits are now correctly formatted. Thank you for your contribution!

[zx8]

FWIW from poking around the issue tracker, I think the generally accepted term for this is "tug" rather than "bump"? Longer term jj enthusiasts are welcome to jump in and correct me though!

[PhilipMetzger]

please drop the conventional commit message prefix and replace it with cli bookmark: or just bookmark: <your-title> since conventional commits explicitly are mentioned in the contributing message guidelines.

[glehmann]

This is a feature that could be useful as a plain command, but IMO it should reproduce the behavior described in #5568 (reply in thread)

[obayemi]

This is a feature that could be useful as a plain command, but IMO it should reproduce the behavior described in #5568 (reply in thread)

Thx, I didn't see this discussion.

I'm not really convinced about the specificities of the behaviour in the discussion though
I think It might be depending on preferences and workflow, but In my opinion, limiting the tug to changes both with description and non empty is needlessly limiting

I should probably talk about it in the discussion though.

[glehmann]

limiting the tug to changes both with description and non empty is needlessly limiting

Maybe we missed something. Could you share a use case where you would want to push an empty commit?