The project directory must be set up in the early stage, the storyboards must be separated, and only one person can modify each storyboard. When cocospod manages third parties, do not transfer the pod folder to the server. Font, color value, button size, unified macros
The most important thing when multiple people develop a project is to solve the problems of code synchronization and merging, so you need to pay attention to the following:
First of all, you should summarize the various scenarios for using SVN commands based on the specific situation of your code management, and summarize a set of SVN command usage guidelines or specifications for different scenarios. To make it easier for newcomers to get started and to prevent code management chaos caused by unreasonable use of SVN.
Then, the project structure should be reasonable to divide functional modules more clearly and reduce module coupling. In this way, different people develop different modules, and there is less chance of conflicts during code synchronization and merging.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The project directory must be set up in the early stage, the storyboards must be separated, and only one person can modify each storyboard.
When cocospod manages third parties, do not transfer the pod folder to the server.
Font, color value, button size, unified macros
The most important thing when multiple people develop a project is to solve the problems of code synchronization and merging, so you need to pay attention to the following:
First of all, you should summarize the various scenarios for using SVN commands based on the specific situation of your code management, and summarize a set of SVN command usage guidelines or specifications for different scenarios. To make it easier for newcomers to get started and to prevent code management chaos caused by unreasonable use of SVN.
Then, the project structure should be reasonable to divide functional modules more clearly and reduce module coupling. In this way, different people develop different modules, and there is less chance of conflicts during code synchronization and merging.
Also, why not use Git?
Don’t use storyboard
I think everything you said above is correct, but I think the most important thing is not to use branches like git, it will be more miserable
Git must use branches. How can you merge without branches?
Multiple backups!
Multiple backups!
Multiple backups!
Say important things three times.