When contributing to this repository, please first discuss the change you wish to make via issue, email or any other method with the owners of this repository before making a change. Please note we have a code of conduct, please follow it in all your interactions with the project.
-
Ensure any install or build dependencies are removed before the end of the layer when doing a build.
-
Pull request message format: [Fixes done] #[issue number] [Description of the issue]
-
Wait for the maintainers to review your pull request and do the changes if requested.
Commits
- Write clear meaningful git commit messages.
- Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at https://github.com/blog/1506-closing-issues-via-pull-requests )
- When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. This makes it very easy for the reviewers and you'll also get reviews quicker.
Feature Requests and Bug Reports
-
When you file a feature request or when you are submitting a bug report, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.
-
Please follow the templates when posting a issue.
-
Feature_Request / Bug_Report - [includes in repository]
-
Would you like to work on the issue?
- Yes
- No
- Other:
-
Join the development
- Before you join development, please set up the project on your local machine, run it and go through the application completely.
- If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to drop in a comment so that the issue can be assigned to you if the previous assignee has dropped it entirely.
- Feel free to Ask Anything! 😎 [Gitter]:https://gitter.im/scorelab/ [homepage]:https://github.com/scorelab/