Node.js Core Utilities
CLI tools for Node.js Core collaborators.
git-node: Custom Git commands for working with Node.js core, e.g. landing Pull Requests.
ncu-config: Configure variables for node-core-utils to use.
ncu-team: Listing members of a team, synchronizing special blocks in files with the list of members.
get-metadata: Retrieving metadata for a Pull Request. DEPRECATED: use
git node metadatainstead.
ncu-ci: Parse the results of a Jenkins CI run and display a summary for all the failures.
npm install -g node-core-utils
If you would prefer to build from the source, install and link:
git clone email@example.com:nodejs/node-core-utils.git cd node-core-utils npm install npm link
Setting up credentials
Most of the tools need your GitHub credentials to work. You can either
- Run any of the tools and you will be asked in a prompt to provide your username and password in order to create a personal access token.
- Or, create a personal access token yourself on GitHub, then set them up using an editor.
If you prefer option 2, follow these instructions to create the token.
When creating the token, the following boxes need to be checked:
user:email: Used by
get-metadatato read the email of the PR author in order to check if it matches the email of the commit author.
read:org: Used by
ncu-teamto read the list of team members.
You can also edit the permission of existing tokens later.
After the token is generated, create an rc file with the following content:
Note: you could use
ncu-config to configure these variables, but it's not
recommended to leave your tokens in your command line history.
Make sure your credentials won't be committed
Put the following entries into
# node-core-utils configuration file .ncurc # node-core-utils working directory .ncu
.ncu/land could contain your access token since it contains the
If you ever accidentally commit your access token on GitHub, you can simply revoke that token and use a new one.
If you encounter an error that you cannot fix by yourself, please
- Make sure you update NCU to the latest version
- Try again with the
NCU_VERBOSITY=debugenvironment variable set and open an issue at https://github.com/nodejs/node-core-utils/issues with detailed logs.
MIT. See LICENSE.