|
| 1 | +<!-- This file is automatically added by @npmcli/template-oss. Do not edit. --> |
| 2 | + |
| 3 | +# Contributing |
| 4 | + |
| 5 | +## Code of Conduct |
| 6 | + |
| 7 | +All interactions in the **npm** organization on GitHub are considered to be covered by our standard [Code of Conduct](https://docs.npmjs.com/policies/conduct). |
| 8 | + |
| 9 | +## Reporting Bugs |
| 10 | + |
| 11 | +Before submitting a new bug report please search for an existing or similar report. |
| 12 | + |
| 13 | +Use one of our existing issue templates if you believe you've come across a unique problem. |
| 14 | + |
| 15 | +Duplicate issues, or issues that don't use one of our templates may get closed without a response. |
| 16 | + |
| 17 | +## Pull Request Conventions |
| 18 | + |
| 19 | +### Commits |
| 20 | + |
| 21 | +We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). |
| 22 | + |
| 23 | +When opening a pull request please be sure that either the pull request title, or each commit in the pull request, has one of the following prefixes: |
| 24 | + |
| 25 | + - `feat`: For when introducing a new feature. The result will be a new semver minor version of the package when it is next published. |
| 26 | + - `fix`: For bug fixes. The result will be a new semver patch version of the package when it is next published. |
| 27 | + - `docs`: For documentation updates. The result will be a new semver patch version of the package when it is next published. |
| 28 | + - `chore`: For changes that do not affect the published module. Often these are changes to tests. The result will be *no* change to the version of the package when it is next published (as the commit does not affect the published version). |
| 29 | + |
| 30 | +### Test Coverage |
| 31 | + |
| 32 | +Pull requests made against this repo will run `npm test` automatically. Please make sure tests pass locally before submitting a PR. |
| 33 | + |
| 34 | +Every new feature or bug fix should come with a corresponding test or tests that validate the solutions. Testing also reports on code coverage and will fail if code coverage drops. |
| 35 | + |
| 36 | +### Linting |
| 37 | + |
| 38 | +Linting is also done automatically once tests pass. `npm run lintfix` will fix most linting errors automatically. |
| 39 | + |
| 40 | +Please make sure linting passes before submitting a PR. |
| 41 | + |
| 42 | +## What _not_ to contribute? |
| 43 | + |
| 44 | +### Dependencies |
| 45 | + |
| 46 | +It should be noted that our team does not accept third-party dependency updates/PRs. If you submit a PR trying to update our dependencies we will close it with or without a reference to these contribution guidelines. |
| 47 | + |
| 48 | +### Tools/Automation |
| 49 | + |
| 50 | +Our core team is responsible for the maintenance of the tooling/automation in this project and we ask contributors to not make changes to these when contributing (e.g. `.github/*`, `.eslintrc.json`, `.licensee.json`). Most of those files also have a header at the top to remind folks they are automatically generated. Pull requests that alter these will not be accepted. |
0 commit comments