Put Git to work: increase the quality of your project
summary
Shows concrete Git automation: uses pre-commit hook to run RuboCop and abort bad formatting, a prepare-commit-msg hook to prepend branch names, and a pre-push script that runs tests only for changed files, cutting a 5‑minute suite down to ~10 seconds locally. Shares hooks via shared-git-hooks (npm postinstall). Implements a bare-repo + post-receive hook that fetches, bundle/yarn installs, migrates, compiles assets and restarts — a minimal Heroku-like deploy that works in production.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:35What you need to do
- 3:13How it can help
- 5:38Git hooks
- 9:19Precommit hook
- 9:59Commit hook
- 10:57Story time
- 12:30Commit message hooks
- 13:32Test before sharing
- 13:48Test only for changed files
- 16:34Shared Git hooks
- 19:59Too much automation
- 22:35Storytime
- 24:23Hook
- 25:11Continuous Integration
- 25:47Integration Servers
- 26:52Continuous Integration Servers
- 27:40Notification
- 29:06Jenkins
- 29:50HP Labs
- 31:42IntelliJ
- 32:58Bamboo
- 33:51Deployments
- 35:34Heroku
- 36:08My goto
- 36:39Create a director
- 37:08Deploy
- 40:37Git Deploy Comment
- 42:21Git Questions
related talks
38m5 ways Git can be used to automate your ruby application deployment
05mBetter Living through Git Hooks
30mLearn how to never commit $%@ to Git
16mHow To Make A "Perfect" Git Commit
01h 08mHow Effective Teams Use Git
01h 39mMastering git collaboration -A DevOps necessity
46mCommit like a Pirate
42mUsing Git like a pro