- DO NOT work on the master branch. This branch is only for functional code and assumes the project is deployable.
- Always create a branch when working on an issue. The name of the branch should be informative. For example, if you are working on an issue titled Create Login Page, name the branch as create-login-page (you get the idea).
- After you have resolved the issue by submitting a pull request, DO NOT make new commits. The reviewers will check the request and on successful resolution, will merge the branch with the Master and delete the branch you were working on.
- When working on an issue, commit frequently with detailed explanations and commit messages so it's easy to track.
- Use suitable Issue Labels when raising an issue. Always add the milestone and project related to the issue if available.
- Use issue keywords to resolve issues automatically when making commits or making a pull request.
- Use Wiki to write technical and project progress reports. This would also contain an exhaustive manual on better managing workflow.
See Documentation for more guidelines.
See Marketplace for useful apps to facilitate better management.
See Projects for managing tasks.
For Python: see requirements.txt to adhere to the correct versions to prevent conflicts between different development groups.