- Where Developers Learn, Share, & Build Careers
I'm sure there is a group of GIT users out there that had this problem:
- < Li> Create a branch from the master We call it featureX .
- While working on, featureX , you feel that you want to fix the previous commit:
- You work your right.
- You do your rebase and squash / fix.
- Later you would like to resize your master with the latest changes in featureX
- Break things because your branches are separated (fixing was not done in the master). You have a bad day.
This is the second time with me that for the first time, I did not have too much history in featureX and was just a new branch of the Master of this But what do you have to do? How do you solve it? Is it possible that
git reset a certain referral? In that case, I can undo the Rebase and move it properly to decide on the top of featureX (using the interactive rebase).
I'm sure there are different ways to go about this, but I think this is a common problem.
Before (refael) because your fix up is still in FeatureX, if you do not fix it, Rebase will not behave differently - it is only important when the master's deviation facility fights with any commission in the X branch - fixup or not.
Secondly, when people first learn GIT, then fall in love with the novelty of resizing. But I've gone back to the merger. It is easy, it has come in the form of history as it happened and it compels some discipline. Here's my workflow:
- Break things because your branches are separated (fixing was not done in the master). You have a bad day.
Comments
Post a Comment