First off, thank you for considering contributing to Boost My Project Network! It's people like you that make Boost My Project Network such a great community.
We have a Code of Conduct in place that we expect all contributors to adhere to. Please read the full text to understand what actions will and will not be tolerated.
-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
-
Open a new issue with a clear list of what you want to add. Include as many details as possible.
-
Remember, the more effort you put into your proposal, the more effort we can put into evaluating it.
-
Fork the repository and create your branch from
main. -
Make your changes.
-
Make sure your code lints and screen shot captured in required devices.
-
Issue that pull request!
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or fewer
- Reference issues and pull requests liberally after the first line
All JavaScript must adhere to JavaScript Standard Style.
- Use Markdown.
This section lists the labels we use to help us track and manage issues and pull requests.
| Label Name | Description |
|---|---|
bug |
Confirmed issues or issues that are very likely to be bugs. |
feature-request |
Feature requests. |
good-first-issue |
Good for newcomers. |
help-wanted |
Extra attention is needed. |