@@ -166,3 +166,11 @@ The editor module [`RWTHVRToolkitEditor`](https://git-ce.rwth-aachen.de/vr-vis/V
...
@@ -166,3 +166,11 @@ The editor module [`RWTHVRToolkitEditor`](https://git-ce.rwth-aachen.de/vr-vis/V
Currently, no such features are implemented.
Currently, no such features are implemented.
# [Development](Home/Development)
# [Development](Home/Development)
Please read the [Development](Home/Development) section carefully. As a summary:
- Use your own forks for developing features to not spam branches on this repository, keep it limited to release and dev branches.
- Use conventional commit syntax when commiting to improve readability for others: `<type>(scope): description`
- Keep commits encapsulated to one change/feature. Don't try to put all your changes into one commit, it makes the history and git blame absolutely unreadable, and git bisect doesn't work as well for debugging.
- Commit changes to shared blueprints early and put up PRs regarding them early. The longer they sit, the more nightmareish merging will become.
- Document your features both in code and in the Wiki.
