Empty `.nvmrc` file at repo root, inconsistent documentation in various repo files

[hesreallyhim]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

This appears to be a repository/tooling guidance inconsistency rather than a single end-user docs article. There is an empty .nvmrc file at the repo root. And there is a doc that mentions .node-version which is in .gitignore.

Relevant locations:

• https://github.com/github/docs/blob/main/src/codeql-cli/README.md#dependency-matrix
• https://github.com/github/docs/blob/main/.github/CONTRIBUTING.md
• https://github.com/github/docs/blob/main/.nvmrc
• https://github.com/github/docs/blob/main/package.json

What changes are you suggesting?

Description:

Inconsistent documentation about Node setup across various docs. Empty .nvmrc file in this repo root. Makes it harder to contribute, although the package.json entry is clear enough, the .nvmrc file may lead a developer to invoke nvm use.

Current inconsistency:

• .nvmrc exists but is empty.
• src/codeql-cli/README.md says Node version is specified in .nvmrc.
• .github/CONTRIBUTING.md references .node-version.
• CI/setup and runtime checks use package.json (engines.node).

Suggested update:

1. Update docs to reference package.json engines.node (or whichever source is intended).
2. Update .github/CONTRIBUTING.md to reference the same canonical source.
3. Either populate .nvmrc with an intended value or remove .nvmrc and any references to it.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.