version control - git branching practices -
I am using GET for a visual studio solution. Here's the structure.
myProject.Domain, myProject.Common, myProject.Core, webClientForCustomer1, is webClientForCustomer2
means as names, web client projects depend on the domain, general and core projects I create a new web client app for every customer and optimize the UI. I add new features to the other three projects, so web client projects need to be updated with new features.
What are your suggestions for modeling my repositories in the branches?
"Is there a model in my repository branch?"
"Destructive Rupees" representation of branches is very suitable for identifying different groups of files
A branch specially Guit or other VCS, for which there is a first-class citizen, which is the method of separate from your other parallel work. The branches do nothing for you because you have my project xxx directories, but because you want to separate your development efforts from other activities (like maintaining your current application, fixing, Refactoring, and on)
Plus, with Git, there is also the notion of publication (for other Git repositories).
One on that issue
Comments
Post a Comment