... | ... | @@ -30,14 +30,44 @@ by three dots "..." and finalized by the smallest common package folder. |
|
|
|
|
|
action/short-message
|
|
|
|
|
|
action is going to one of the actions defined above.
|
|
|
short-message should be one to four word seperated by a dash "-"
|
|
|
|
|
|
feat/create-tournament
|
|
|
fix/member-not-found
|
|
|
refactor/move-match-test
|
|
|
enhance/calculating-match-result
|
|
|
docs/format-review
|
|
|
|
|
|
## Merge requests
|
|
|
|
|
|
merge request title should follow the formatting for commit messages
|
|
|
|
|
|
action(package): message
|
|
|
*See commmit for more information*
|
|
|
|
|
|
A .gitlab directory will contain the configuration and templates for merge requests.
|
|
|
Type of information that each merge request must contain is:
|
|
|
Short description of what the merge request changes or adds.
|
|
|
Description of what some of the key changes do. Using javadoc is acceptable.
|
|
|
A list of all methods changed or added.
|
|
|
Label the change as tiny, small, medium, large.
|
|
|
Description of type of change or addition. At least one of the following needs to be added.
|
|
|
|
|
|
|
|
|
It should be written as class/location
|
|
|
|
|
|
### subject of change
|
|
|
- method
|
|
|
- inheritence
|
|
|
- field
|
|
|
- test
|
|
|
|
|
|
Statistics/method-field-inheritence-test
|
|
|
- list of affected parts of the code; method names, field names etc.
|
|
|
Added class Statistics that tracks results in additon to times recieved a red card.
|
|
|
|
|
|
|
|
|
## Issues
|
|
|
|
|
|
When writing an issue, it is important to go into as much detail as possible. For example when describing a bug, add as much information as possible. When requesting a feature, describe your idea, who it would benefit, and if possible: how to implement it.
|
... | ... | |