-
Notifications
You must be signed in to change notification settings - Fork 38
Labels
Appropriate labels should be put on all pull requests (PRs) and issues.
If the PR/issue is related to the backend of the application.
For issues that report bugs, and for PRs that fix the reported bug.
If the PR/issue is related to creating design documentation
If the PR/issue is related to creating documentation of the project.
If the issue is a duplicate of another. Ensure the other issue is linked.
If the PR/issue is related to the addition of a new feature to the application.
If the PR/issue is related to the frontend of the application.
If the issue is for a piece of work that is not intended to be "done," but is instead an ongoing piece of work done throughout the whole project. If the PR is related to such an ongoing issue (i.e. if the PR does not intend to close the issue).
If the PR/issue is not related to changing or adding functionality, but instead refactoring the code.
If the PR/issue is for making changes that aide development and won't have a user impact.
If the PR/issue is related to testing. If the PR is for an enhancement that also has some unit tests, this label is not needed.
-
GitHub Workflow
- Full Team Meetings
- Design Team Meetings
- Frontend Team Meetings
- Backend Team Meetings