Skip to content

Latest commit

 

History

History
25 lines (16 loc) · 1.04 KB

maintaining.md

File metadata and controls

25 lines (16 loc) · 1.04 KB

Maintaining

Testing

  • npm test: Lint the code and run the entire test suite with coverage.
  • npm run test-win: Run the tests on Windows.
  • npm run coverage: Generate a coverage report for the last test run (opens a browser window).
  • tap test/fork.js --bail: Run a specific test file and bail on the first failure (useful when hunting bugs).

Release process

  • Bump dependencies.
  • Ensure Travis CI and AppVeyor are green.
  • Publish a new version using np with a version number according to semver.
  • Write a release note following the style of previous release notes.

Pull requests

  • New features should come with tests and documentation.
  • Ensure the contributing guidelines are followed.
  • At least two team members must LGTM a pull request before it's merged.
  • Squash commits when merging.