-
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.
-
If possible, use the relevant bug report templates to create the issue.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Before submitting, please ensure that
- The code has been formatted and passes linting (
npm run lint
) - A test case has been added and it passes (
npm run test
)
-
Suggest your change by creating an issue (unless one exists already) on the issues page and start writing code.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Before submitting, please ensure that
- The code has been formatted and passes linting (
npm run lint
) - A test case has been added and it passes (
npm run test
)
- Ask any question on the issues page.
The extension is being developed solely on the author's free time. I encourage you to contribute if you want to see a specific feature added!
Thanks! ❤️ ❤️ ❤️
Tomi Turtiainen