stackabletech / stackabletech/stackable-utils
Add tool to manage branch protection rules across many repositories
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 2
- 派生
- 1
- PR 合并指标
- 30 天内没有已合并 PR
描述
We currently have a branch protection rule in place that protects "release-*" branches in our repositories.
This has drawbacks:
- it will cause release scripts to fail because the newly created release branches cannot be pushed to by the script
- prs on these branches cannot use the merge queue (not possible with wildcards in the branch name)
It might be worth switching to individual protection rules for every release, but that would make them hard to change/administer.
The github api allows managing these rules: https://docs.github.com/en/rest/branches/branch-protection?apiVersion=2022-11-28
We should look into writing a simple python script that takes a list of repos and release names and updates these protection rules.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 issue 中链接的 GitHub branch protection REST API 开始,确定如何管理多个存储库的保护规则。将脚本输入定义为存储库列表和 release 名称列表;完成的标准是可以集中更新规则,而不依赖 release-* 通配符,从而使 release 推送和合并队列正常工作。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, python
- 领域
- devops, release
- Issue 类型
- 功能
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100