Comic book continuity and Git rebase
summary
Uses Git rebase to keep feature branches replayed onto the latest master so pull requests produce a linear canonical history that avoids broken commits and speeds git bisect. Jenkins and Travis run tests, spin up immutable demo nodes per branch, and auto-deploy tagged releases to staging and production. Workflow permits rebasing locally and a force-push feature branch after resolving conflicts. Claimed result: small distributed teams (reported workable up to ~100 devs) get continuous deploys, cleaner history, and fewer integration surprises.
AI-written summary · about
chapters (11)
- 0:00Introduction and philosophy
- 3:27The comic book metaphor
- 8:57Bridging comics and Git
- 11:41Technical workflow deep dive
- 15:49Practical implementation
- 20:13Git mechanics and terminology
- 23:25The integration cycle
- 28:34Handling conflicts and history
- 33:44Benefits of clean history
- 37:02Conclusion and resources
- 39:59Q&A session
related talks
42mUsing Git like a pro
01h 39mMastering git collaboration -A DevOps necessity
26mLightning Branches - A Way to Supercharge Your Feature Delivery
55mContinuous Deployment Workflows for Modern JavaScript
05mGit as a continuous manager
01h 08mHow Effective Teams Use Git
21mFighting Git Workflows
01h 08mHow Effective Teams Use Git