Skip to content

Latest commit

 

History

History
21 lines (11 loc) · 1.22 KB

CONTRIBUTING.md

File metadata and controls

21 lines (11 loc) · 1.22 KB

Where to Find Known Issues

We are using GitHub Issues for our public bugs. We keep a close eye on this and try to make it clear when we have an internal fix in progress. Before filing a new task, try to make sure your problem doesn’t already exist.

Proposing a Change

If you intend to change or add features, or make any non-trivial changes to the implementation, we recommend filing an issue. This lets us reach an agreement on your proposal before you put significant effort into it.

If you’re only fixing a bug, it’s fine to submit a pull request right away but we still recommend to file an issue detailing what you’re fixing. This is helpful in case we don’t accept that specific fix but want to keep track of the issue.

learn to submit pull requests by this post or this video

Before submitting a pull request

  1. You must format your code by a formatter like prettier or beautify.

  2. The code must be provided with comments and explanations.

  3. You must provide descriptive variable names.

  4. You must test it before publishing.