Fighting Git Workflows
summary
A 16‑year Windows codebase of 3 million lines and a ~20‑developer team migrates from SVN to Git/GitLab and runs two 6 months experiment workflows: A (SVN‑like merge into master, QA on master) and B (feature‑branch QA, frequent rebases). The team adopts auto‑rebase and merge via GitLab bots, Jira sync and CI pipelines; it reduces manual merging but forces frequent rebases, creates long‑lived branch pain, and drives heavy build load requiring beefy servers. The automation works but is not a silver bullet.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:47Some context
- 4:06OUR TEAM ON SVN
- 6:54Merging vs. Rebasing
- 12:08When to integrate changes
- 17:47GitLab Runner Pipeline
- 18:06GitLab Pipeline Scheduler
- 18:51MR behind master
- 20:07Tools & People
related talks
27mModern Source and Version Control with Git
30mJourney To The Cloud
21mGit Good – How knowing git can make your life easier
27mDevOps Days MTL 2019 - Christian Couder
46mComic book continuity and Git rebase
01h 22mGit-ting along with others
01h 39mMastering git collaboration -A DevOps necessity
01h 08mHow Effective Teams Use Git
