News for hackers. Stuff that matters.
Re:Jujutsu for Busy Devs by 1718627440 on Tuesday July 22, 2025 @06:15AM (#44645141)
For me a merge is about grouping commits, when you have just a list of commits, the list can be very long.

That's also useful for bisecting, as you can first find the feature that is buggy and then find the commit that introduced it.

Re:Jujutsu for Busy Devs by globular-toast on Tuesday July 22, 2025 @06:42AM (#44645304)
The whole point of bisect is to make it quicker to find a point in a potentially long list of commits. Finding the feature first then bisecting within the branch is only going to make it slower, and requires you to manually restart the bisect.

I use the commit message to add ticket numbers to things to group commits.

Re:Jujutsu for Busy Devs by 1718627440 on Tuesday July 22, 2025 @07:17AM (#44645500)
The commits surrounding them (logically) are probably also relevant, which you will find easier when you have grouped commits by features.

I prefer to have everything in a single source of truth (git), so everything is in commits. Your tickets are my merge commits.