- While creating an issue make sure to keep the title simple.
- Please elaborate on the issue in the description as much as possible in depth.
- Please assign the issue to a valid user you know could resolve the issue.
- Assign a due-date to the issue.
- assign an applicable label to the issue.
- Assign a milestone if necessary.
- Open an issue using the steps mentioned above about the pull-request
- Create a merge-request from the issue-page itself
- Assign one of the following labels - bump-major, bump-minor, bump-patch
- Develop and push commits on the new branch
- Once ready to merge, assign an approver and resolve the WIP status.
- Do not squash-commits and always delete branch.
- Please make commits with small changes - makes it easy to review and follow
- Please be elaborate in your commit messages - it costs nothing
3. Do not use skip-ci or its variants in the commit-message. Doing so, will skip the pipeline and thus cause the version update to be out of sync.
Master is updated only through merge-requests which follow the above discipline. The labels bump-major, bump-minor and bump-patch are absolutely necessary labels for any merge-request since they define the next version number. The repository follows the simple [semantic versioning scheme](https://semver.org/).