Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Man, 99% of non-bug-fix commits don't have a why other than "advance the current task".

Almost all commits live in tandem with some large feature or change being made. The reason for absolutely all of them is the same - build the thing .



>other than "advance the current task"

How do you expect someone to know what “the current task” was when they’re tracking down a bug 2 years down the line?


Then write that and link to the current task. That's the why. You don't need an LLM for that.


Perhaps this is about commit granularity. If keeping the history about advancing the task is not useful, then I’d merge these commits together before merging the PR; in some workflows this is set up to happen automatically too.


Maybe what we need is a pre-commit hook that prefixes every commit with the name of the branch it's being made onto




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: