4 ms·
Not anything ”harmful” but for example committing when I don’t want it to commit on its own.
by victorbjorklund 2mo ago
Not anything ”harmful” but for example committing when I don’t want it to commit on its own.
- sandcat_ 2mo agoI'd use a hook to forbid that.
- wvenable 2mo agoCommit is the line I don't let the LLM cross. There's no reason for it commit; that's the part where I check its work.
- AussieWog93 2mo agoUsually I will ask the LLM to commit only the work it just did, in case the worktree is dirty. It also tends to write actual in-depth commit messages too.
- black3r 2mo agocommits are local, so they're okay to me, I draw the line at pushing them... I either want to check its work while it's working, or let it finish and then check it all at once -> if it splits it work into smaller commits its easier for me to review it before pushing than if it was just uncommitted hundreds (or thousands) of lines of code all across the codebase.
- wvenable 2mo agoOften I find I want to correct the LLM; I think it makes more sense to do that before the commit. I don't want to commit a bunch of half-baked work even if it is just local.