" Dave Farley (co-author of ‘Continuous Delivery’) describes Continuous Integration as the process of automatically creating a potential release candidate after every commit. Are feature branches going to help you do that? "
I think so, if you build a feature outside of the main branch, test it fully and prepare it correctly, the commit to the main branch will be a potential release candidate. You can't say that if you are integrating a potentially broken feature into the main branch everyday.
I've never seen a git crew work in isolation before. If two teams or people are working on two different modules that need to work together they are still integrating between themselves on a regular basis. It's just that those changes do not get pushed up to main until they are finished.
I think so, if you build a feature outside of the main branch, test it fully and prepare it correctly, the commit to the main branch will be a potential release candidate. You can't say that if you are integrating a potentially broken feature into the main branch everyday.
I've never seen a git crew work in isolation before. If two teams or people are working on two different modules that need to work together they are still integrating between themselves on a regular basis. It's just that those changes do not get pushed up to main until they are finished.