I have a very different requirement managing multiple release branches (unlike Git-Flow or using Master as only release branch). As i'm not a CLI expert so want to learn how can i achieve my requirements using Source Tree.
I'm quite sure that you guys will help me overcome these issues, thanks :)
Here is a very simple explanation of my problem.
- ill have a baseBranch with a paid code from third party.
- ill have another child branch of baseBranch which will have custom version (custom code edits etc) of that paid code and we name it "customCode".
- ill have another child branch of "customCode" and will name it "customDesign" so paid code now have custom design changes.
- Now i'll will have multiple branches of "customDesign" for different clients and each branch will b a release branch for that client .
Now this branch system will work as "OOP" where a superclass cant have a subclass functionality, but sub class may have super class functionality or override it.
Having said that:
- Merging will never work from bottom to top, .'s changes will never go into   .
- Merging may work from top to bottom. For example, if i update paid code from third party in . then ill b able to merge it back to  BUT keep my custom changes intact (Partial Merging).
- Same above rule apply from  to .
Please advise how can i do that using Source Tree.
Thanks again :)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG