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