3 ms·
This. This is the correct way to think about it. Ballooned feature branches suck either at merge time or at deployment time. The problem in either case isn't t
by jroseattle 11y ago
This. This is the correct way to think about it.
Ballooned feature branches suck either at merge time or at deployment time. The problem in either case isn't the model -- it's the balloon of changes.
Commit early and often -- and merge back to master. :-)
- Silhouette 11y agoThis argument assumes that useful changes can always be broken down into bite-sized chunks and implemented incrementally without unwanted side effects. That's an ideal situation, and it's also a realistic one a lot of the time, but not always. A development process that can't cope with major changes being needed from time to time isn't going to be appropriate for a lot of projects.