As we move the development of this project into an open-source repository, it will be imperative that we have a commit guide that outlines our commit review process. This guide should include instructions for developers regarding how to branch the project and how to name branches. This should also include the review process and how we perform quality control. If we reject a merge request, the third-party developer should be able to read the commit guide/review process and understand why their request was rejected.
As we move the development of this project into an open-source repository, it will be imperative that we have a commit guide that outlines our commit review process. This guide should include instructions for developers regarding how to branch the project and how to name branches. This should also include the review process and how we perform quality control. If we reject a merge request, the third-party developer should be able to read the commit guide/review process and understand why their request was rejected.