This repository was archived by the owner on Dec 19, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Conventions
ayishacs edited this page Feb 10, 2021
·
6 revisions
- Author: Author is responsible for the creation, assignment, pull requests, approvals, merging and closing of the issue.
- Contributor: Contributor provides additional support to Author with feedback, resources, and additional support if requested.
- Reviewer: Reviewers provide feedback, reviews and approve the pull request to merge changes to the dev and main branch.
- Release manager: Release manager is responsible for the project creation, maintaining Kanban Boards for the project and updating the status of each card as we progress in each milestone.
- We have created the
devbranch for development purposes, which would be merged into themainbranch after every milestone. - Each feature/bug would have a separate branch.
Pull requests have to be approved by at least one person before they can be merged into the dev or the main branch.
- Each commit should have the issue number to which the commit belongs
- No one can commit directly to the
devor themainbranch. All commits must happen through PRs.
Each task or bug should be created as an issue. We have created the following tags for better categorization of issues: design, documentation, bug, and so on.
Milestones