cs101:tortoisesvn:tortoisesvn
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cs101:tortoisesvn:tortoisesvn [2020/10/27 13:31] – [Working with the checked out repository] localadmin | cs101:tortoisesvn:tortoisesvn [2020/10/27 18:26] (current) – [Checking out a Working Copy] localadmin | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Getting Started with TortoiseSVN ===== | ===== Getting Started with TortoiseSVN ===== | ||
- | TortoiseSVN is GNU General Public License software that you can download for free. It is available for both 32-bit and 64-bit Windows. | + | TortoiseSVN is GNU General Public License software that you can download for free. It is available for both 32-bit and 64-bit Windows. |
==== Basic SVN Concepts ==== | ==== Basic SVN Concepts ==== | ||
Line 13: | Line 13: | ||
Subversion maintains a central database which contains all your version-controlled files with their complete history. This database is referred to as the repository. The repository normally lives on a file server running the Subversion server program, which supplies content to Subversion clients (like TortoiseSVN) on request. | Subversion maintains a central database which contains all your version-controlled files with their complete history. This database is referred to as the repository. The repository normally lives on a file server running the Subversion server program, which supplies content to Subversion clients (like TortoiseSVN) on request. | ||
| | ||
- | === Working Copy === | + | === Working |
This is where you do your actual work. Every developer has his own working copy, sometimes referred to as a sandbox, on his local PC. You can pull down the latest version from the repository, work on it locally without affecting anyone else, then when you are happy with the changes you made commit them back to the repository. | This is where you do your actual work. Every developer has his own working copy, sometimes referred to as a sandbox, on his local PC. You can pull down the latest version from the repository, work on it locally without affecting anyone else, then when you are happy with the changes you made commit them back to the repository. | ||
Line 43: | Line 43: | ||
You should then get an Authentication box where you input your login and password you use for your SVN account. **Only leave the Save Authentication checkbox checked if on a private computer!** | You should then get an Authentication box where you input your login and password you use for your SVN account. **Only leave the Save Authentication checkbox checked if on a private computer!** | ||
- | {{: | + | {{: |
You'll now see the progress of the checkout. All files and the folders that are included in the checkout will be logged. | You'll now see the progress of the checkout. All files and the folders that are included in the checkout will be logged. | ||
Line 61: | Line 61: | ||
* {{: | * {{: | ||
* {{: | * {{: | ||
+ | * {{: | ||
+ | |||
+ | ==== Common Problems ==== | ||
+ | Occasionally you may get a conflict when you update/ | ||
+ | |||
+ | There are two kinds of conflicts: | ||
+ | * File conflicts | ||
+ | * A file conflict occurs if two (or more) developers have changed the same lines of a file. This can also occur if one developer is working on code from two different computers. | ||
+ | * Tree conflicts | ||
+ | * A tree conflict occurs when a developer moved/ | ||
+ | Just remember to always do an update before working on a file. | ||
+ | |||
+ | To address conflicts, you can either launch an external merge tool / conflict editor with TortoiseSVN --> Edit Conflicts or you can use any text editor to resolve the conflict manually. You should decide what the code should look like, do the necessary changes and save the file. Using a merge tool such as TortoiseMerge or one of the other popular tools is generally the easier option as they generally present the files involved in a 3-pane view and you don't have to worry about the conflict markers. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== Committing (Saving) Your Changes with TortoiseSVN ===== | ||
+ | |||
+ | Before you commit your changes, it is good practice to ensure your working (local) copy is up to date with the repository. To update your working copy, select the desired files or directories, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When you have ensured your working copy is up to date, it's time to add your changes to the repository. Select the desired files or directories and hit the SVN Commit… command. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | SVN Commit… will open the commit dialog where you can perform a number of actions: | ||
+ | * Add a log message from the commit dialog. It's good practice to leave a log message as they can be useful if problems arise later. | ||
+ | * Prevent a particular file from being committed by unchecking the file. | ||
+ | * Show the log of previous actions. | ||
+ | * Hit OK to commit your changes to the repository. | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | A commit dialog box will open showing the result of the commit process. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | More help can be found from [[https:// | ||
+ | |||
+ | |||
+ | |||
+ | Loppu |
cs101/tortoisesvn/tortoisesvn.1603823482.txt.gz · Last modified: 2020/10/27 13:31 by localadmin