4 ms·
I like some of this, but I worry about rebasing that often after pushing. I understand the benefit of keeping the history cleaner, but it also means if any feat
by etherealG 15y ago
I like some of this, but I worry about rebasing that often after pushing. I understand the benefit of keeping the history cleaner, but it also means if any features are worked on by multiple people it would become impossible to use git's best feature of auto merging things.
What do you do when feature work is long standing and worked on by multiple people?
- zmanji 15y agoWhat do you do when feature work is long standing and worked on by multiple people? In this case there should be a topic branch for the big feature and all development comes off that branch. You can simply replace master with the topic branch and topic branch with your personal branch and this model will work.
- etherealG 15y agobrilliant idea, thanks :)