Skip to content

Latest commit

 

History

History
50 lines (32 loc) · 2.03 KB

CONTRIBUTING.md

File metadata and controls

50 lines (32 loc) · 2.03 KB
Raw

Code of Conduct

FullHuman has adopted the Contributor Covenant Code of Conduct for all of its project. Please read the text so that you understand how to conduct while contributing to this project.

Semantic Versioning

Purgecss use SemVer for versioning.

Documentation

The content of the documentation is in the purgecss-docs repository.

Sending a Pull Request

Before submitting a pull request, please make sure the following is done:

  1. Fork the repository and create your branch from master.
  2. If you've added code that should be tested, add tests!
  3. If you've changed APIs, update the documentation.
  4. Ensure the test suite passes (npm test).
  5. Format your code with prettier (npm run prettier).
  6. Make sure your code lints (npm run lint).
  7. Run the Flow typechecks (npm run flow).

Development Workflow

After cloning Purgecss, run npm i to fetch its dependencies. Then, you can run several commands:

  • npm run dev will build cjs and es module of Purgecss in the lib folder and watch for changes.
  • npm run lint checks the code style.
  • npm test runs the complete test suite.
  • npm test -- --watch runs an interactive test watcher.
  • npm test <pattern> runs tests with matching filenames.
  • npm run flow runs the Flow typechecks.
  • npm run build creates the cjs and es module of Purgecss in the lib folder.

Make sure that your pull request contains unit tests for any new functionality. This way we can ensure that we don't break your code in the future.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Aknowledgement

This CONTRIBUTING.md is based on the react how-to-contribute.md file.