Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
anroven3657yGood moment to learn something! You can Google how to undo things like that. Git can be very forgiving if you know its advanced features.
-
hawkes15727yBut didn't development branch off from master anyway? You would only get changes on master which are not in your branch.
(Oh, and ... rebasing > merging!) -
hawkes15727yControlled rebasing makes the repo less cluttered. Google for "gitflow" for a workflow fit for larger projects.
In short: While you are developing a feature, rebase your branch on master instead of merging to get changes of other devs into your feature branch, when the feature is finished merge the branch back to master.
When you rebase you also resolve conflicts on a commit-by-commit base instead of resolving one huge conflict.
If you develop a feature with 7 commits and have 5 merge commits from master to your branch, and you push that stuff to stay in the repository history forever - I don't know who you are, but I will find you, and I will ... force you to learn git! -
vadimir2007yi don't get the problem. as long as you only merged there shouldn't be any problems with said branch. considering you haven't made changes to the master branch directly in which case i would say that you deserve it
I just merged master branch INTO my development branch. Fuuuuuuuck
undefined