In order to have a repository that developers can feel fully confident in using, implementing CI / CD (Continuous Integration / Continuous Deployment) into this utility is required.

Automation simplifies developers contribution concerns since it operates 24/7/365 and provides them with instant feedback on their contributions. It also improves the repository's core by preventing human errors from being introduced.

To achieve this, the core code must have a satisfactory amount of test coverage, the services for CI/CD must be connected, and we may need to modify the branching strategy employed currently to have a proper staging area as well. Discussions on how best to approach this are welcomed.