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: CONTRIBUTING.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,10 +39,10 @@ Also, we use [ESLint](https://eslint.org/) for clean and stylistically consisten
39
39
40
40
**Pull requests are not merged unless all quality checks are passing.** At minimum, `format`, `lint`, `typecheck`, and `knip` must all be green before a pull request can be merged. Run these locally before opening or updating a pull request:
41
41
42
-
-`npm run fmt:check`
43
-
-`npm run lint`
44
-
-`npm run typecheck`
45
-
-`npm run knip`
42
+
-`pnpm run fmt:check`
43
+
-`pnpm run lint`
44
+
-`pnpm run typecheck`
45
+
-`pnpm run knip`
46
46
47
47
## Restrictions on Generative AI Usage
48
48
@@ -62,7 +62,7 @@ We use [Knope](https://knope.tech/) with the Knope GitHub Bot to manage change d
62
62
63
63
If you have used [Changesets](https://github.com/changesets/changesets) before, Knope should feel very similar. The main difference is scope: Changesets is typically used for JavaScript repositories because it relies on `package.json`, while Knope is multi-language.
64
64
65
-
If you prefer, you can install the Knope CLI yourself using the [official installation guide](https://knope.tech/installation/). This repo also exposes the CLI through npm scripts, so you can run `npm run knope -- <subcommand>` (for example: `npm run knope -- document-change`). Otherwise, this repo installs Knope for you via `postinstall`, so running `npm i` is enough.
65
+
If you prefer, you can install the Knope CLI yourself using the [official installation guide](https://knope.tech/installation/). This repo also exposes the CLI through pnpm scripts, so you can run `pnpm run knope -- <subcommand>` (for example: `pnpm run knope -- document-change`). Otherwise, this repo installs Knope for you via `postinstall`, so running `pnpm i` is enough.
66
66
67
67
### Documenting a change
68
68
@@ -72,8 +72,8 @@ For user-facing pull requests, add one before requesting review.
72
72
73
73
CLI paths:
74
74
75
-
-`npm run document-change`
76
-
-`npm run knope -- document-change`
75
+
-`pnpm run document-change`
76
+
-`pnpm run knope -- document-change`
77
77
-`knope document-change` (if Knope is installed locally)
78
78
79
79
All commands open an interactive prompt; fill in the package, change type, and short summary, then commit the generated change file in your PR.
@@ -112,11 +112,11 @@ Releases are driven by Knope Bot (`[bot.releases].enabled = true`):
112
112
113
113
Maintainers can preview behavior without changing files:
114
114
115
-
-`npm run knope -- release --dry-run`
115
+
-`pnpm run knope -- release --dry-run`
116
116
117
117
You can also validate the local Knope config with:
118
118
119
-
-`npm run knope -- --validate`
119
+
-`pnpm run knope -- --validate`
120
120
121
121
**For any query or design discussion, join our [Matrix room](https://matrix.to/#/#sable:sable.moe).**
0 commit comments