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 摘要。