node-core-utils
node-core-utils copied to clipboard
nodejs
CLI tools for Node.js Core collaborators
After two consecutive releases in which I mistakenly pushed a broken release commit to main, I'm convinced that the process needs improvement. This PR proposes to add a reminder to...
Sometimes I get bothered by the cross references automatically created by GitHub cluttering the referenced PR/issue, especially when they get copied into various forks and each fork would generate a...
When using `git node release --prepare --security` for the upcoming security release, the tool broke when including the .patch to the proposal
Currently, the `request-ci` only works for approved PRs. This is annoying because: - collaborators cannot approve their own PRs, and have to wait for someone else to approve their PR...
Add a new `git node staging` command that automates cherry-picking commits into staging branches. It works by cherry-picking all commits that have no conflicts and stopping when finding commits that...
I am on a new laptop and forgot some configs in my project specific config and failed the `cq` due to column length > 72 characters, therefore decided to land...
FYI I just created a ruleset for this repo: https://github.com/nodejs/node-core-utils/settings/rules/4654889 It targets the default branch and enables: - Restrict deletions - Require linear history - Require a pull request with...
Allows PR author (or repo maintainers) to define themselves the Notable Change using a `` section in the PR description. We should also update the workflow that comments when the...
On my computer, I have several git worktrees (one for `main`, one for each release line, etc). The promotion fails on the "cherry-pick to main" step, because I'm running it...