Git Branching Model
summary
Describes branch-organization strategies for Git: recommends using git-flow for packaged releases but finds it too heavy for continuous-delivery e-commerce and proposes two alternatives—a simplified git-flow and an environment-tied “liscio flow” that map branches to staging/test/production. Advises tooling (GitHub, GitLab, Bitbucket and trackers like Jira, Trello, ClickUp, Teamwork) and gives ten practical rules including running tests per commit, protecting main, using pull requests, tagging releases manually, referencing task IDs in commits, writing intentful messages, keeping a changelog, and not deleting important branches.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:14Git branches
- 6:10Git Flow
- 10:08Git Flow pros and cons
- 14:22Git Flow for small projects
- 16:11Trunk Flow for environments
- 20:09Choosing the model
- 23:21Repo rules
- 31:45Q&A
- 42:58Summary
