SC E04 — Git Environmentalism: Protect Our Branches

Summary

Addresses a maturing analytics team problem: developers bypassing version control by committing directly to master during urgent situations. Walks through the cascade of failures this creates — production breaks, frenzied fixes, merge conflicts, team confusion. Proposes GitHub Branch Protection as the solution: require pull requests, enforce code reviews, mandate status checks, include administrators in restrictions, and limit merge permissions.

Core philosophy: “friction-free deployments” matter more than rapid individual commits. Uptime and accuracy are essential to organizational trust.

Key Arguments

• Fire drills create shortcuts that cause bigger fires
• Branch protection rules add process but prevent costly errors
• Administrators should not be exempt from restrictions — equal accountability
• A second set of eyes (code review) catches what urgency blinds
• Trust in the analytics platform depends on deployment discipline

Writing Style Notes

The “environmentalism” framing is playful — protect branches like you’d protect the environment. Practical and prescriptive with a clear problem-solution structure. Aimed at analytics teams adopting engineering practices.

Connections

• 01-projects/newsletter/index — early Sanity Check, engineering practices for analytics teams