You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ Then:
88
88
-**Do not modify** the root `mocha.js` file directly; it is automatically generated.
89
89
- Keep your PR focused.
90
90
Don't fix two things at once; don't upgrade dependencies unless necessary.
91
-
1. Before committing, run `npm start test`.
91
+
1. Before committing, run `npm test`.
92
92
- This will run both Node.js-based and browser-based tests.
93
93
- Ultimately, your pull request will be built on our continuous integration servers ([GitHub Actions](https://github.com/mochajs/mocha/actions?query=workflow%3A%22Tests%22)).
94
94
The first step to ensuring these checks pass is to test on your own machine.
Copy file name to clipboardExpand all lines: .github/DEVELOPMENT.md
-2
Original file line number
Diff line number
Diff line change
@@ -16,5 +16,3 @@ If you are having trouble, don't be afraid to [ask for help](./CONTRIBUTING.md#
16
16
- Do not use `yarn install` or `pnpm install`.
17
17
- Some optional dependencies may fail; you can safely ignore these unless you are trying to build the documentation.
18
18
- If you're sick of seeing the failures, run `npm install --ignore-scripts`.
19
-
20
-
> PRO TIP: After `npm install`, run `npm start` to see a list of commands which can be run with `npm start <command>` (powered by [nps](https://npm.im/nps)).
0 commit comments