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
feat: allowlist for version numbers in YAML comments (#172)
* feat: allowlist for version numbers in YAML comments
If an environment variable `NODE_RELEASED_VERSIONS` is detected, it is
used to validate the version numbers in the YAML comments. At the
notable exception of version numbers 0.0.x and 0.1.x, and the
`REPLACEME` placeholder, any value not in the list is reported as
invalid.
The idea is to use this in a GitHub Action. It will generally not affect
running the linter locally.
Copy file name to clipboardExpand all lines: README.md
+28-6Lines changed: 28 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,12 +20,34 @@ npm test
20
20
21
21
### Adding the language to the documentation style guide
22
22
23
-
1. PR the [nodejs/node](https://github.com/nodejs/node) repo adding the language/grammar to the [documentation style guide](https://github.com/nodejs/node/blob/master/doc/guides/doc-style-guide.md)
23
+
1. PR the [nodejs/node](https://github.com/nodejs/node) repo adding the
1. In [node-lint-md-cli-rollup](https://github.com/nodejs/node/tree/master/tools/node-lint-md-cli-rollup), bump the `remark-preset-lint-node` dependency
30
-
1. In the `nodejs/node` repo, rebuild the Markdown linter (`make lint-md-rollup`)
31
-
1. PR the `nodejs/node` repo with the updated linter
0 commit comments