nodejs / nodejs/node-core-utils
Suggestion: auto-land and auto-release NCU Pull Requests
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 314
- 派生
- 137
- 平均合并
- 2 天 8 小时
- 30 天内合并 PR
- 24
描述
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 in this repository. Similarly, sometimes commits will sit on master for a while until someone has time to publish a new version on npm. My suggestions:
- A scheduled GitHub Action that will merge all PRs with at least one approval and green CI. This could run every 5 minutes (quickest the scheduler can run), or maybe every hour (since we don't have a big flow of PRs here).
- A scheduled GitHub Action that will make a new release to npm every day (if we want quick releases) or every week (if we want slower releases)
We would need to identify semverness of PRs somehow, either via labels or using https://www.conventionalcommits.org/en/v1.0.0/. Looking at our logs, we're already not strictly following Node.js core commit guidelines and we have mixed Node.js and conventional commit messages.
As for npm releases, it might be tricky because we require 2FA. If anyone worked with 2FA and automated npm releases before, I'd be happy to see solutions :)
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先检查仓库现有的 GitHub Actions 和 npm 发布设置,然后比较拟议的审批、CI、semver、调度和 2FA 要求。要视为完成,必须先就自动化和发布策略达成一致,之后才能确定实现范围。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github-actions, javascript, nodejs
- 领域
- ci-cd, devops, release
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100