Neither the code nor the AI know WHY a commit it being made.

This context should at the very least be linked.

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 .

	▲	kace91 9 hours ago \| parent \| next [-]
		>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?
	▲	crabmusket 9 hours ago \| parent \| prev \| next [-]
		Then write that and link to the current task. That's the why. You don't need an LLM for that.
	▲	merelysounds 4 hours ago \| parent \| prev [-]
		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.