Want to contribute to Beagle Web? There are a few things you need to know.
Submit all changes to master branch. Always base your work on the project's master branch, naming your new branch according to the following guide:
feature/branch-namefor new featuresfix/branch-namefor fixing a bug
We are using GitHub Issues for our public bugs. Before filing a new task, try to make sure your problem doesn’t already exist.
Before sending us a pull request, please make sure the following is done:
- Run yarn in the repository root
- If you’ve fixed a bug or added code that should be tested, add tests
- Ensure the test suite passes (yarn test)
- Make sure your code lints (yarn lint)
Help us review your PRs more quickly by following these guidelines.
- Try not to touch a large number of files in a single PR if possible.
- Don't change whitespace or line wrapping in parts of a file you are not editing for other reasons. Make sure your text editor is not configured to automatically reformat the whole file when saving.
- Reviewers will check the staging site and contact you to fix eventual problems.