Commit like a Pirate
summary
A tool called Captain Hook ships as a PHP and native Go binary, installs local git hook scripts (users must opt in), and enforces Chris Beams commit rules via a built-in message must follow Beams rules validator. Configuration is a JSON file with placeholders for staged files, per-hook action lists, and overridable local settings. It adds virtual hooks like post-change, supports Go async parallel runs, and is used to run pre-push unit tests — annoying to teammates but effective at catching regressions.
AI-written summary · about
chapters (11)
- 0:00Introduction to GitHooks
- 3:08Commit message rules explained
- 7:46GitHooks setup challenges
- 11:41Introducing Captain Hook
- 18:49Virtual hooks and conditions
- 23:03Installing Captain Hook
- 26:38Placeholders and best practices
- 31:03Configuration overrides
- 33:12Advanced use cases and examples
- 35:04Pre-push hook benefits
- 40:00Q&A and closing
related talks
05mBetter Living through Git Hooks
43mPut Git to work: increase the quality of your project
30mLearn how to never commit $%@ to Git
16mHow To Make A "Perfect" Git Commit
25mUsing Git Hooks to Help Your Engineering Teams Work Autonomously
38m5 ways Git can be used to automate your ruby application deployment
25mAutomatic Checks for the People
28m"Git hook[ed]” on images & up your documentation game