github / github/github-ospo

Remembering what we've already done

未關閉
#98 0 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視
enhancement ospo-actions
主要語言
沒有語言資料
星號
749
分支
72
PR 合併指標
30 天內沒有已合併 PR

描述

### Is your feature request related to a problem?

Several of our actions run into the problem of working through the first X number of repos in an organization when they fail due to rate limiting or max action run times. If they could save state or remember what repos have been evaluated recently, that would be helpful for delivering more value for each action. This happens especially for OSPOs that are working on the "get clean" phase of any task rather than the "stay clean". ie. Every repo in an org of 10k repos needs a dependabot PR opened. (evergreen)

### Related OSPO Tool

automatic-contrib-prs GitHub Action, cleanowners GitHub Action, evergreen GitHub Action, issues-metrics GitHub Action, stale-repos GitHub Action

### Describe the solution you'd like

Ideas:
- A dump/file saved of repos processed and then an upload for the next run.
- Separate out the scan all repos/get repo list from the action that should be taken into separate actions
- database something something hand wave

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

貢獻指南

開啟貢獻指南

研究方向

先檢視 issue 中提到的 GitHub Actions:automatic-contrib-prs、cleanowners、evergreen、issues-metrics 和 stale-repos。比較提出的 state file、split-action 和 database 方案,接著定義已處理的儲存庫如何在執行之間持續保存,以及後續執行如何在大型組織中繼續工作。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
github-actions
領域
devops
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。