Better Living through Git Hooks
summary
Walks through concrete hook scripts: use the repository's hooks directory, remove the .sample suffix and add a bash script so pre-commit runs tests and blocks a commit when tests fail, while commit-msg enforces message format and prepare-commit-msg can edit autogenerated merge messages. Demonstrates that failing tests leave changes staged (so fixes can be amended) and that post-commit can trigger builds or deploys; shows the sample files and literal commands used.
AI-written summary · about
chapters (4)
related talks
43mPut Git to work: increase the quality of your project
16mHow To Make A "Perfect" Git Commit
30mLearn how to never commit $%@ to Git
46mCommit like a Pirate
38m5 ways Git can be used to automate your ruby application deployment
36mCommit Messages to the rescue!
28m"Git hook[ed]” on images & up your documentation game
42mUsing Git like a pro