Use of SVN version management tools

1. svn download

https://tortoisesvn.net/downloads.html download site

http://www.cnblogs.com/xiaobaihome/archive/2012/03/20/2407610.html Learning website

2. Use steps

1. Install VisualSVN-Server (administrator installs the server side)

2. Ordinary developers install the client SVN After installation, " tortoiseSVN " will appear in any folder by right-clicking , if not, restart the computer

3. Start VisualSVN manager and right-click on Repositories --> create new Repository ---> keep the default options --> warehouse name --> complete (the warehouse file must not be deleted) Add a new user to the user

3. Client operation

1. Create a local repository

    (1) Create a new project folder "project", right click on "project"--->SVNCheckout--->Get the url address of the warehouse from the server: For example: https://Lenovo-PC/svn/st/

    (2) Click the first item of accept

    (3) Enter username and password

    (4) Click: checkout

    (5) After returning to the previous directory, you will find a green tick in the folder.

    (6) If hidden files can be displayed in the directory, a .svn folder will appear.

2. Add files or folders

    (1) Newly created file --- will display a blue ? sign, indicating that the file has not been submitted to the server.

    (2) Right-click in the blank: --- > SVN commit ----> commit

    (3) Select the documents to be submitted and fill in the description information. ----"ok

    (4) The file turns green, indicating that the submission was successful

3. Modify the file

(1) After modifying the local file, it will turn red!

(2) After modification, right click, commit , and submit again

4. Delete files

(1) After deleting the file or folder locally, commit it again

5. Pull the file

(1) Create a repository for the first time, use SVN checkout. Then pull the server file later, use SVN update .

6. Version rollback

(1) Right-click --- > tortoiseSVN ----> show log ------> find the version to be rolled back-----> right-click ---- > revert to this revision ----- >Click revert to roll back to the specified version

7. Conflict resolution

(1) If there is a conflict in the submission, then ok---->update----->generate four files---->cancel

(2) The four files are: A and B are in conflict, A's own, before B submits, and after B submits.

(3) Open the conflict file, resolve ---> delete the other three ----> commit

(4) Remind other relevant personnel to update again

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325375607&siteId=291194637