Skip to content

Latest commit

 

History

History
33 lines (19 loc) · 1.57 KB

CONTRIBUTING.md

File metadata and controls

33 lines (19 loc) · 1.57 KB
Raw

Contribution Guidelines

Want to contribute to BingeBond? Here are some guidelines for how we accept help.

Getting in Touch

Our Telegram group is the best place to ask questions or get advice on building Wander.

Submitting a Pull Request

  1. Fork and clone the repository.
  2. Comment on the issue that you are gonna take up, indicating the approximate time you would take to finish it.
  3. After finishing, push to your fork and submit a pull request.
  4. Wait for your pull request to be reviewed and merged.
  5. In the meantime you can take up other issues as well.

Reporting Bugs and Issues

We use GitHub Issues to track bugs, so please do a search before submitting to ensure your problem isn't already tracked.

New Issues

Please provide the expected and observed behaviours in your issue.

Proposing a Change

If you intend to implement a feature, or make a non-trivial change to the current implementation, we recommend first filing an issue marked with the proposal tag, so that the engineering team can provide guidance and feedback on the direction of an implementation. This also help ensure that other people aren't also working on the same thing.

Bug fixes are welcome and should come with appropriate test coverage.

License

By contributing to Wander, you agree that your contributions will be licensed under its MIT license.