48 ms·
For small, integrated teams, github flow may be suboptimal. Frequent merging to master, aka trunk-based development, aka Continuous Integration is the way to go
by gocartStatue 6y ago
For small, integrated teams, github flow may be suboptimal. Frequent merging to master, aka trunk-based development, aka Continuous Integration is the way to go for me.
- chii 6y ago> trunk-based development, aka Continuous Integration continuous integration isn't trunk-based development (where everyone merges into the same master branch)!
- gocartStatue 6y agoI love pasting that quote :) "The idea that developers should work in small batches off master or trunk rather than on long-lived feature branches *is still one of the most controversial ideas in the Agile canon*, despite the fact *it is the norm in high-performing organizations such as Google.* Indeed, many practitioners express surprise that this practice is in fact implied by continuous integration, but it is: The clue is in the word “integration.” [State of DevOps report 2016]