nodejs / nodejs/node-core-utils
Branch protection improvements
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 313
- 派生
- 137
- 平均合并
- 2 天 8 小时
- 30 天内合并 PR
- 24
描述
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 at least one approval
- Block force pushes
Only the pull request requirements are new compared to the old branch protection rule (https://github.com/nodejs/node-core-utils/settings/branch_protection_rules/17880641)
I think we can delete that rule. The only thing that remains in it is the restriction of who can push and that only restricts the nodejs-github-bot account. I don't think there's a convenient way to port that to rulesets. We could use the bypass list but then every pull request would always be red and require collaborators to click the bypass checkbox.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
检查链接的 GitHub 仓库设置页面中的规则集,并将其与现有的分支保护规则进行比较。确认旧规则中对 nodejs-github-bot 的 push 限制是否可以替换或移除,同时不影响 pull request。完成的标准是仓库具有预期的单一分支保护配置。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github
- 领域
- devops
- Issue 类型
- 功能
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 30/100