News for hackers. Stuff that matters.

A comment on The Git history command deserves more attention. Parent comment

Re:The Git history command deserves more attention by CuriouslyC on Tuesday July 14, 2026 @06:46AM (#48904748)
Making small atomic commits as you go in the age of AI tends not to go great because it forces too much human in the loop in a lot of cases, and the percentage of AI code rework is significantly higher than manual code, so the history tends to be harder to keep clean.

It's ironically easier to create a messy agent work branch then have the agent cherry pick independent PRs from it into atomic commits post-work.

[ Parent | on HN ]
Re:The Git history command deserves more attention by locknitpicker on Tuesday July 14, 2026 @09:15AM (#48906369)
> Making small atomic commits as you go in the age of AI tends not to go great because it forces too much human in the loop in a lot of cases (...)

You seem confused. In the age of AI your ai code assistants already do task-specific commits. In fact, you can easily create a skill to have ai do that for you. It can even use git history split.

You see where this is going?

[ Parent | on HN ]