@@ -44,7 +44,22 @@ Some projects collaborating with outside groups are on GitHub (i.e. ph5)
Repositories stored in GitLab are backed-up off-site nightly.
## 2.1 Branch naming and commit comments
TODO
### 2.1.1 Branch Naming
### 2.1.2 Commit Comments
In order to create a useful revision history, all developers should follow a set of rules for commit comments. These rules will define:
- Style: Markup syntax, wrap margins, grammar, capitalization, and punctuation.
- Content: The information that should or should not be in the commit message's body.
- Metadata: The reference to issue tracking IDs, pull request numbers, etc.
Split the commit messages into subject and body. Use the following 7 rules to create a proper commit message for different projects. A diff will tell you what changed, but only the commit message can properly tell you why.
1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how
## 2.2 Branching Model:
Master should be stable, trusted and field worthy. And releases should be tagged on master.
