To myself: sometimes I think the background process should be committing for me automatically each time a new working set exists, and I should only rebase and squash before pushing.
That’s reversing the flow of control, but might be workable!
jj already pretty much does that with the oplog. A consistent way of making new snapshots in the background would be nice though. (Currently you have to run a jj command — any jj command — to capture the working directory.)
wrs|26 days ago
stavros|26 days ago
sfink|26 days ago
I don't recommend it, though, at least not on large repositories. Too much opportunity to collide with command-line jj write operations.