CONTRIBUTING.md

Contributing Guide

Thank you for investing your time in contributing to our project! Any contribution you make will be reflected on the project's NPM page ✨.

In this guide, you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

New contributor guide

To get an overview of the project, read the README file. Here are some resources to help you get started with open-source contributions:

• Finding ways to contribute to open source on GitHub
• Set up Git
• GitHub flow

Issues

Create a new issue

If you spot a problem with the package, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using the issue form.

Solve an issue

Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. See "Label reference" for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.

Make Changes

Make changes locally

1. Fork the repository.

• Using GitHub Desktop:

  • Getting started with GitHub Desktop will guide you through setting up Desktop.
  • Once Desktop is set up, you can use it to fork the repo!

• Using the command line:

  • Fork the repo so that you can make your changes without affecting the original project until you're ready to merge them.

2. Install or update to Node.js to the project version.

3. Create a working branch and start with your changes!

Commit your update

Commit the changes once you are happy with them. Double-check that you have staged all of the files you want to commit and that you are committing to the correct branch to speed up the review process ⚡

Pull Request

When you're finished with the changes, create a pull request, also known as a PR.

• Don't forget to link PR to issue if you are solving one.
• Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a contributor will review your proposal. We may ask questions or request additional information.
• We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, and then commit them to your branch.
• As you update your PR and apply changes, mark each conversation as resolved.
• If you run into any merge issues, check out this git tutorial to help you resolve merge conflicts and other issues.

Your PR is merged!

Congratulations 🎉🎉 I personally thank you for your contribution ✨.

Once your PR is merged, your contributions will be publicly visible on the NPM page.