Labels

• area: async

  related to asynchronous use of Mocha
• area: browser

  browser-specific
• area: documentation

  anything involving docs or mochajs.org
• area: integrations

  related to working with 3rd party software (e.g., babel, typescript)
• area: node.js

  command-line-or-Node.js-specific
• area: parallel mode

  Regarding parallel mode
• area: reporters

  involving a specific reporter
• area: repository tooling

  concerning ease of contribution
• area: security

  involving vulnerabilities
• area: usability

  concerning user experience or interface
• area: website

  involving mochajs.org, but not necessarily involving docs
• area: windows

  Windows-specific
• autorelease: pending
• autorelease: tagged
• core-team

  issues which must be handled by Mocha's core team
• dependencies

  Pull requests that update a dependency file
• duplicate

  been there, done that, got the t-shirt...
• faq

  a frequently asked question or common misconception
• future

  needs to wait
• good first issue

  new contributors should look here!
• invalid

  not something we need to work on, such as a non-reproducing issue or an external root cause
• landed-on-v6.2.x

  cherry-picked on v6.2.x branch from master
• landed-on-v7.1.x

  cherry-picked from master
• nice to have

  enhancement proposal of low priority
• run-browser-test

  run browser tests on forked PR if code is safe
• semver-major

  implementation requires increase of "major" version number; "breaking changes"
• semver-minor

  implementation requires increase of "minor" version number; "features"
• semver-patch

  implementation requires increase of "patch" version number; "bug fixes"
• stale

  this has been inactive for a while...
• status: accepting prs

  Mocha can use your help with this one!