Xiaobai asks a question
There is currently a project A that is developed based on the needs of customer a. Due to business expansion, the products of project A are also used by customer b. However, customer b has some personalized needs and will branch out based on project A. Project B
Then the question is, how should I manage the project so that when I change project A, I can simultaneously change the same parts of project B while retaining personalization (currently using svn, if git can solve it better, I can consider changing it)
1
0
0
According to experience, merging code and using it on two such projects usually does not produce good results.
Two projects are two independent projects. There should be two projects, not different branches in one project.
Branch is suitable for the process of developing features. I personally think it is not suitable for such a scenario of providing products to users A and users B respectively.
Just maintain the two projects manually.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
