docs: Update commit documentation

Author: caffeine-addictt

.github/CODESTYLE.md

@@ -57,21 +57,27 @@ class ExampleClass:
 
 
 ## Commit Message Guidelines
-When committing, commit messages are prefixed with a `+` or `-`. Depending on the type of change made 
-influences which prefix is used.
-
- - `+` when something is added.
- - `-` when something is removed.
- - none: when neither is applicable, like merge commits.
+When committing, commit messages are prefixed with one of the following depending on the type of change made.
+
+ - `feat:` when a new feature is introduced with the changes.
+ - `fix:` when a bug fix has occurred.
+ - `chore:` for changes that do not relate to a fix or feature and do not modify *source* or *tests*. (like updating dependencies)
+ - `refactor:` for refactoring code that neither fixes a bug nor adds a feature.
+ - `docs:` when changes are made to documentation.
+ - `style:` when changes that do not affect the code, but modify formatting.
+ - `test:` when changes to tests are made.
+ - `perf:` for changes that improve performance.
+ - `ci:` for changes that affect CI.
+ - `build:` for changes that affect the build system or external dependencies.
+ - `revert:` when reverting changes.
 
 Commit messages are also to begin with an uppercase character. Below list some example commit messages.
 
+```sh
+git commit -m "docs: Added README.md"
+git commit -m "revert: Removed README.md"
+git commit -m "docs: Moved README.md"
 ```
-git commit -m "+ Added README.md"
-git commit -m "- Removed README.md"
-git commit -m "Moved README.md"
-```
-
 
 
 ## Markdown Guidelines