About the use of svn;

the new frontend talent starts his internship. He has used git but knows nothing about it. He only knows how to upload the code, regardless of the trunk branch. Today, the team leader briefly talked about trunk and branch;. I don"t know if he understood it. He asked me to create two folders, one is trunk and the other is branch;, which asked me to develop in branch to form a good habit. Then I pulled a project, which is in trunk and in branch. He told me to develop, update and submit in branch; update as soon as I come every day, and then submit it when I leave; my understanding is that branch is our current development environment, messing around in it. But I don"t quite understand the trunk folder, and I pulled the same project; but what"s the use? I do it in branch every day; whether it"s submit or update; I haven"t touched the project in that trunk; I"ve asked them once or twice that it"s easy, but I still don"t understand it.

Dec.22,2021

trunk means trunk. Some teams are used to developing on the trunk, and some teams are used to developing on the branch. You obviously belong to the latter. After the development on the branch is completed, someone (not necessarily you) merges to the trunk, which has the advantage of ensuring a relatively stable backbone code.


you may need this.
Visual Learning git


trunk you have not moved, but you can directly merge your code into, this is not necessarily your operation.


We open it under branch, and then submit it to trunk after testing.
branch and trunk are actually specifications for writing code. For example, if your current online code is trunk, and you want to develop new features, then develop it on branch, so that the code does not affect each other
you can take a look at these two
https://www.cnblogs.com/keyi/.

articles.
Menu