Submitting patches

Do you have an awesome change to quick-lint-js you want to contribute back to the maintainers? Let's get your patch out there!

Pre-submit checklist

• Tests pass on your machine.
• Code adheres to the coding standards.
• New automated tests are included. (Tests are only necessary bug fixes and features.)
• Documentation is updated, if appropriate.
• Code is checked into Git as one commit or a small number of commits.
• Commits have a description explaining what the problem was and what the solution is. The first line of the commit follows Conventional Commits. Use git log to see examples.

Submitting the patch

quick-lint-js maintainers prefer to receive a GitHub pull request with your patches. If you are new to using GitHub, check out freeCodeCamp's guide to creating your first pull request.

If you prefer to submit your patch discreetly, send an email to strager.nds@gmail.com.