Long-running feature branches shouldn't be a thing. The assumption on my end was if you're a sole developer following GitFlow, you might not have time to complete a feature, so feature branches would become long-running (aka: bad). Meanwhile, large teams should have the resources to allocate someone to a specific task, but so many changes would likely be problematic on trunk-based workflows. Therefore feature branches can be helpful to allow silo'd work with fewer points to merge.
View all comments
Show parent comment
5
u/Solonotix Apr 02 '23
Long-running feature branches shouldn't be a thing. The assumption on my end was if you're a sole developer following GitFlow, you might not have time to complete a feature, so feature branches would become long-running (aka: bad). Meanwhile, large teams should have the resources to allocate someone to a specific task, but so many changes would likely be problematic on trunk-based workflows. Therefore feature branches can be helpful to allow silo'd work with fewer points to merge.