5 ways Git can be used to automate your ruby application deployment
summary
Five concrete techniques: use pre-commit hooks to run RuboCop and abort bad commits, rewrite commit messages to prefix branch names, and run only the tests for changed files before push which cuts feedback time dramatically. Install hooks across machines with the shared-git-hooks npm shim, add a post-receive deploy hook on a bare repo to run bundle/yarn/assets and restart services, and call CI via webhook. These steps prevent broken builds, speed deploys, and have saved production rollbacks.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:13Put Git to work
- 8:53Life is too short to test before sharing my code!
- 13:30Trick'em into using your perfect hooks
- 20:16Continuous integration pooling?
- 37:22Questions?
related talks
43mPut Git to work: increase the quality of your project
36mContinuous Deployment with Rails
05mGit as a continuous manager
05mBetter Living through Git Hooks
34mGuide to Continuous Deployment with Rails
01h 08mHow Effective Teams Use Git
32mContinuous Integration and Deployment: Five Lessons Learned
29mFearless DevOps: Committing to Code
