Participation in this open source project is subject to the npm Code of Conduct.
Please also ensure your contribution conforms to the Contributing Guidelines.
- Find an issue you would like to solve. If you are solving a problem that does not have an issue filed yet, file one.
- Fork and clone the project. Solve the problem!
- (if relevant) Document any changes you made in the correct place.
- (if relevant) Write a test to show your solution solves the problem.
- Open a PR. Somewhere in the body it should say
Fixes #<issue>, where#<issue>is the issue number of the issue you are closing.
The commit history of a project should read like that project's recipe. Commit messages should be written in the active present tense, e.g.,:
fix typo in how-npm-works dedupe section
Other items:
- You will be asked to squash your commits.
- Rebase is preferred over merge.
Note: Everything in git can be fixed, so don't be intimidated by these requirements! We're here to help you through it, if you need it :).
your-first-pr: reserved for people with little to no GitHub contributions- we're here to help you start your OS journey!patches welcome: these issues are specifically well suited for outside contributors.