Drivy's engineering team moved away from Git Flow after adopting Heroku Pipelines, which made the master branch redundant in their release process. Their simplified flow uses feature branches merged into master, with CI auto-deploying master to staging, and any developer promoting staging to production when ready. The post covers bundling multiple commits into a single release, handling cases where commits need to be held back, and performing hotfixes by checking out the latest production tag and branching from there.

5m read timeFrom marcgg.com
Post cover image
Table of contents
Moving Away From Git FlowWhy Not Use The Github Flow?Our Simple Git Flow

Sort: