Using Git Hooks to Help Your Engineering Teams Work Autonomously
summary
Zalando migrates from SVN to Git starting late 2013 and replaces a brittle, centralized server hook with an optional local system that enforces but doesn’t block workflows. It uses a Python update hook to reject branch pushes while allowing other branches, builds turnstile local hooks as an open-source, extensible installer, and solves scale by filters out already-checked commits plus JVM pooling for style checks so large pushes stop blocking the server.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:34The Age of the Git Hook - First Plan • A common code base for git and syn
- 4:49The Age of the Git Hook - First Feedback • Git is not SVN
- 5:51The Age of the Git Hook - Plan B • A dedicated hook for Git
- 7:17The Age of the Git Hook - Problems
- 14:32The Age of the Autonomy - Turnstile
- 14:45Turnstile - How to install it $ pip install turnstile-core
- 16:11Turnstile - More than a hook • Core subcommands
- 18:32What we learned • Don't get stuck in the past
- 23:02Turnstile - How to use it • Add a turnstile.yml file to your repository
related talks
21mFighting Git Workflows
43mPut Git to work: increase the quality of your project
05mBetter Living through Git Hooks
38m5 ways Git can be used to automate your ruby application deployment
05mGit as a continuous manager
01h 08mHow Effective Teams Use Git
42mUsing Git like a pro
22mUsing Git in an (un)orthodox way in your team
