4 ms·
I suspect that people who are used to working in small, integrated teams are more used to using the github flow (aka, a web tool to do code reviews which also i
by chii 6y ago
I suspect that people who are used to working in small, integrated teams are more used to using the github flow (aka, a web tool to do code reviews which also integrates git commands).
People who are more used to a hub and spoke model - aka, a maintainer receiving tonnes of patches from many different people - would prefer the git email flow (it requires less work from them - patches that don't merge is pushed back to the contributor).
- gocartStatue 6y agoFor 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]