node-core-utils
node-core-utils copied to clipboard
nodejs
CLI tools for Node.js Core collaborators
We have a few rules about commits to our V8 copy, that are documented in the [maintaining V8 guide](https://github.com/nodejs/node/blob/master/doc/guides/maintaining-V8.md). Some things could be easy to check: - For backports /...
Seen here: https://github.com/nodejs/node/pull/35405 When i proceed anyway, each message nevertheless has all requisite info: ``` node on git:v12.x-staging ❯ git rebase upstream/v12.x-staging -i -x "git node land --amend" Executing: git...
Having an up to date ncu is essential for folks to land PRs following the latest process, but today if someone tries to use ncu with an older version it...
A few things that come to mind 1. Show commands spawned by ncu 2. Show HTTP request response, in particular responses that could not be parsed as JSON (e.g. when...
It would be great to already copy the command suggestions into the clipboard (and allow to opt-out of that behavior) by using e.g., https://www.npmjs.com/package/clipboardy
It should be possible to anticipate the next command. For example in case a rebase is needed due to multiple commits. In such case, it would be nice to already...
Right now when changing the commit messages a file is added and that has to be changed. This is not really straight forward: ``` ? Use this message? No Please...
I use `git worktree` a lot, it would be nice if node-core-utils could identify when we're running commands on a worktree and look for `.ncu/` on the main worktree.
So it's easier to know which tests are failing across all platforms. Something like: ``` ------------------------------- Failures Summary ------------------------------- Build failures: - win-vs2017 - cross-compiler-armv7-gcc-6 - osx1011 Test failures: -...
Can be useful when a flaky tests is legitimately failing.