Run file scripts/install-hook.py. It will copy contents of scripts/pre-push-hook.py to .git/hooks/pre-push. Make sure that you have .git/hooks/pre-push.sample in your .git directory before performing this step.
This will install git pre-push-hook in your local .git directory. It will run the commits against linting tests before pushing to a remote. See scripts/pre-push-hook.py if you encounter any errors.
Technology Stack
Please get familiar with the different components of the project in order to be able to contribute.
development
All development goes on in this branch. If you're making a contribution, please make a pull request to development.
PRs must pass a build check and all tests check on Travis.
master
This contains shipped code. After significant features/bug-fixes are accumulated on development, we make a version update, and make a release.
When you make very very minor changes to a PR of yours (like for example fixing a failing travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterwards so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at https://davidwalsh.name/squash-commits-git )
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. It 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 to the Issue tracker, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.
Join the development
Before you join development, please set up the system on your local machine and go through the application completely. Press on any link/button you can find and see where it leads to. Explore. (Don't worry ... Nothing will happen to the app or to you due to the exploring
请发表评论