-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathSVN commit guide.txt
23 lines (16 loc) · 977 Bytes
/
SVN commit guide.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Format for commenting SVN commits:
1. Do not commit without a comment. This is a massive hassle for anyone trying to find the history of a file or folder. Spending ages doing manual code comparisons isn't fun.
2. The first part of each line of your commit message should indicate what time of modification you have done.
ADD - Added a new file/class
CHG - Modified something existing
DEL - Removed something
FIX - Fixed something that was broken
Examples:
An example of a bad commit message is:
Changed some stuff to make it better
An example of a good commit message is:
CHG: AgeingErrors now rebuild. This allows them to use estimables correctly.
CHG: AgeingErrors now build the Matrix slightly differently
CHG: Derived Quantities now rebuild for estimation
CHG: NormalDistribution now uses a static function, no longer inherits from CBaseManager
CHG: AgeingError Unit Tests for Observations merged into a single file.