node-core-utils
node-core-utils copied to clipboard
nodejs
CLI tools for Node.js Core collaborators
As title says, ncu-ci could (optionally) wait for a pending CI and send a desktop notification when it's finished, as well as outputting the result. Something like: ```console $ ncu-ci...
I don't think we have a simple automated way to do that now. Due to the way we land commits in releases, we cannot just search for the commit SHA...
I've been doing `ssh-add -K /path/to/key` for this but it would be nice if git-node can just pipe to stdin (or at least display something more informative about this)
In node-core-utils, we use `node-fetch` to make http requests. But this library doesn't support proxy in its options, which makes requests failed in some cases. Suggestion: using [`request`](https://www.npmjs.com/package/request) or [`got`](https://www.npmjs.com/package/got)...
Which should implement https://github.com/nodejs/node/tree/master/test/wpt#how-to-add-tests-for-a-new-module for a given module with `id`
e.g. ```console $ ncu-ci run node-test-pull-request 12345 ```
We have 12 check suites today on Node.js, which means we're not retrieving all suites to check if they passed (well, after #469 lands). We're retrieving 100 commits for the...
support revert v8 commit by hash, should be usefully when test V8 function. Like https://github.com/nodejs/node/pull/35415#issuecomment-700987060, I have a [guess](https://github.com/v8/v8/commit/fafb4769984690ac87f0183d09973b934b0b74dd), but cumbersome reverting the commit in node.js repo.
Looking at our Pull Requests list, seems like we have six pull requests ready to land (with approvals), but I don't think it's clear who is allowed to land PRs...
Is that something we would be interested in? The tool is only (meant to be) used by collaborators anyway, and capturing some analytics as well as logs and errors could...