Development workflow

Opening a pull request

Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics.
Single commit per pull request
For writing commit messages please check out the following blog post.
Follow uniform design practices. The design language must be consistent throughout the app.
The pull request will not get merged until and unless the commits are squashed. In case there are multiple commits on the PR, the commit author needs to squash them and not the maintainers cherrypicking and merging squashes.
If you don't know how to squash commits, please watch the following video.
If the PR is related to any front end change, please attach relevant screenshots in the pull request description

If you are submitting a new issue please follow the below template

Expected Behavior If you're describing a bug, tell us what should happen If you're suggesting a change/improvement, tell us how it should work
Current Behavior If describing a bug, tell us what happens instead of the expected behavior If suggesting a change/improvement, explain the difference from current behavior
Possible Solution Not obligatory, but suggest a fix/reason for the bug, or ideas how to implement the addition or change
Steps to Reproduce (for bugs) Provide a link to a live example or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant
Context How has this issue affected you? What are you trying to accomplish? Providing context helps us come up with a solution that is most useful in the real world
Your Environment Include as many relevant details about the environment you experienced the bug in
- Version used:
- Environment name and version (e.g. Chrome 39, node.js 5.4):
- Operating System and version (desktop or mobile):
- Link to your project: