Skip to content

Latest commit

 

History

History
25 lines (16 loc) · 1.47 KB

CONTRIBUTING.md

File metadata and controls

25 lines (16 loc) · 1.47 KB

How to Contribute to Lintspec

Did you find a bug?

  • Do not open up a GitHub issue if the bug is a security vulnerability in lintspec, and instead contact the maintainer.
  • 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.

Did you write a patch that fixes a bug?

  • 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.
  • Make sure to add unit tests to avoid regressions.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of lintspec will generally not be accepted.

Do you intend to add a new feature or change an existing one?

  • Suggest your change in a feature request issue and wait on feedback from the maintainers before writing code.
  • Do not open an issue on GitHub until you have collected positive feedback about the change.

Thanks! ❤️ ❤️ ❤️