- clone or fork the repo
- make your own branch (see branch naming style)
- setup a development environment
- make changes
- commit your changes (see commit message naming style)
- make a pull request
- discuss on your changes
- merge ^_^
All of the listed naming rules should be followed. But don't give it too much matter. These rules exist only for keeping the order of the repo and work done on mode development
The repository has adopted the following style of branch naming:
<branch_type>: <functionality_description>
feature/opened_chest_ui
fix/crashing_on_lounch
feature
: new featuers should be implemented hearfix
: any kindes of fixes should be done hear
The repository has adopted the following style of commits:
<commit_type>: <commit_message>
feat: add super duper feature
^--^ ^------------^
| |
| +-> Summary in present tense.
|
+-------> Commit type.
feat
: A new featurefix
: A fix of a piece of functionalitydocs
: Documentation only changesperf
: A code change which improves performancerefactor
: A code change that neither fixes anythingrevert
: A revert to previous commit