Repository updates, issue/MR templates and improved CI
Detailed Description
The repository needs more automation. the CI should handle publishing of packages and running tests. The issues and MR's need templates to make things more organized and consistent.
Context
-
Obviously better organization and more consistency makes things easier for everyone. Issue templates and MR templates help clarify what is being done and why.
-
Automated publishing on new tags will save the trouble of creating npm package mistakes or incorrect versions
-
Automated tests for merge requests will go a long way in ensuring consistent code and that the MR is not going to break any existing code.
Possible Implementation
- Add templates to
.gitlab
directoy - Add package
semantic-version
to automate, publishing to npm, handling versions and creating a changelog etc
Possible Issues/Bugs
- Unit tests are currently broken and need imporvments, this will stop us from creating a test stage in the CI
- We could fix this by updating the unit tests and ensuring they work.
Edited by ltngames