Mono repository. One repository for every project(s) / exercises in the course.
We use topic-branches, such that individual features will be on their own branch. Once the feature is believed to be complete, a pull request will be opened to main, and reviewed by other group members. Once verified, it will be merged into master.
Centralized workflow with shared repository hosted on GitHub.
Commit messages should be written in imperative mood, and should be descriptive of the changes in the commit. Try to adhere to The seven rules of a great Git commit message - Chris Beams
If the subject line of 50 characters is insufficiant to describe the commit, use the commit body. Seperate subject and body with a blank line.
A new feature requires at least one happy-path test for the implemented feature to be merged to main.
Responsibility for integrating/reviewing contributions, rotates among the team of five thhk, jglr, krbh, emja, kaky, on a weekly basis.
| Week | Date | Responsible |
|---|---|---|
| 1 | 7 Feb | thhk |
| 2 | 14 Feb | jglr |
| 3 | 21 Feb | krbh |
| 4 | 28 Feb | emja |
| 5 | 7 Mar | kaky |
| 6 | 14 Mar | thhk |
| 7 | 21 Mar | jglr |
| 8 | 28 Mar | krbh |
| 9 | 4 Apr | emja |
| Easter Break | 11 Apr | kaky |
| 10 | 18 Apr | thhk |
| 11 | 25 Apr | jglr |
| 12 | 2 May | krbh |
| 13 | 9 May | emja |