5
I have a question regarding the organization of GIT.
I have 1 project that will be divided into 2 verses for different clients, I would like to maintain a main branch and that the general changes were made in this branch and replicated for the 2 verses, but each version will have its only changes.
Ideally do with Fork or branches?
I would say that the ideal would be to have a configuration that would follow path A or path B, having two separate source codes can give you a lot of headache (own experience)
– Jefferson Quesado
But then every improvement I’ll have to replicate for N projects, I don’t think it’s smart that. The product is the same, we only have 2 slightly different versions for specific customers.
– RBoschini
Depending on the number of project files that would change for each client, if there are few I believe that using branch can be the fastest and simplest solution. But Fork is the copy of a base project that can be changed freely that in its context seems to be more interesting, even more so if in the future you use the base project for new clients.
– Andre Gusmao
André is my thought, there would be 1 base product with 2 variants for each customer, qlq Generica change is made at the base and replicated for the others. sera is the best way to solve this problem?
– RBoschini
@Rboschini, I think the best way would be for the base project to be designed to accept parameterizations as well as Wordpress and other CMS works. Another way to do it is to develop the base project in a generic way and the variants would have the base project as dependency.
– Andre Gusmao
It would not help, it is an Ecommerce and the biggest variation will be of layout and not of business rules. the api will remain the same, only the front will follow a base that will branch into 2 slightly similar verses. Parameterizing this would not be the best way in this case.
– RBoschini
I ended up solving creating Fork and making Sync with precise qd base project.
– RBoschini