Difference between revisions of "General day to day"
Line 1: | Line 1: | ||
+ | Rough..This is for info on the principles of using version control day to day | ||
− | + | =A Working Cycle= | |
+ | |||
+ | When you are using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code. You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to. Finally, if you are staisfied, you will then want to incorporate your changes into a new latest version of the code. | ||
+ | |||
+ | If you are working collaboratively, it is also a good idea to check that the latest version of the code is working correctly when take a local copy. Also, you may already have a local copy of the code. You will want to update your local copy with any changes committed to the repository since you last updated. | ||
+ | |||
+ | Thus, your normal working cycle will be: | ||
+ | |||
+ | # checkout/update | ||
+ | # test | ||
+ | # edit | ||
+ | # test | ||
+ | # commit |
Revision as of 19:21, 6 February 2006
Rough..This is for info on the principles of using version control day to day
A Working Cycle
When you are using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code. You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to. Finally, if you are staisfied, you will then want to incorporate your changes into a new latest version of the code.
If you are working collaboratively, it is also a good idea to check that the latest version of the code is working correctly when take a local copy. Also, you may already have a local copy of the code. You will want to update your local copy with any changes committed to the repository since you last updated.
Thus, your normal working cycle will be:
- checkout/update
- test
- edit
- test
- commit