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

Running on the working tree is mostly okay - just `exit 1` if changes were made and allow the user to stage+commit new changes. It isn't perfect but it doesn't require checking out a new tree.


What if I've already fixed the format issue (but not staged it). The pre-commit hook will pass, but it's not doing what the author intended (preventing unformated code from being committed).

What if I've only staged one part of a file, but the pre-commit hook fails on the unstaged portions, which should be fine since I'm not commiting or pushing those changes.


You can stash it or `git commit -n`. Perfect is the enemy of good enough.


this completely breaks `git add -p`.


You can either do another `git add -p` after to stage the fixed formatting or do `git add -pn`




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

Search: