Antoine du Hamel
Antoine du Hamel
> Moving these to new files will have an impact on node.js startup time. Why would that be?
CITGM (`main`): https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3492/ CITGM (this PR): https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3494/
I can volunteer to prepare a release this week if there is a volunteer to promote it (because the release proposal for 22.0.0 was frozen some time in advance, there...
Sounds good. I'm probably going to start preparing the release without waiting, as it's my first one ever, I assume I may need to start over anyway – and we...
I went ahead a run an analysis on Node.js codebase. Using the 8232 commits (that's 20% of all the commits that have landed on `main`) that landed at least one...
> This (25% of collaborators inactive for 26 weeks returning, and 10% after 56 weeks) Note that this is contributors, not collaborators (which may or may not be a close...
I've re-run the analysis, with different parameters: - 90% of Node.js contributors have less than 9 contributions. I decided to look into those who have more than 9 contributions (I...
We don't land backports with the CQ, so I don't think that would be problematic. For cherry-picks, I don't think the commit would contain `PR-URL` or `Reviewed-by` trailers, would they?...
I see! So if we started to use that flag in Node.js, we would need to land those PRs manually. Would that disrupt your process?
I guess it would actually not apply for those, since the GHA commit linter is only validating the first commit message, and those floating patches are never first IIRC.