github / github/accessibility-scanner

Proactively address GitHub rate limit restrictions

未关闭
#127 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
TypeScript
星标
373
派生
42
平均合并
1 天 9 小时
30 天内合并 PR
10

描述

A GitHub Copilot action shouldn't ever be set up to allow for rate limiting to come into effect:

Sorry, you've hit a rate limit that restricts the number of Copilot model requests you can make within a specific time period. Please try again in 2 hours. Please review our Terms of Service (https://docs.github.com/site-policy/github-terms/github-terms-of-service). If the problem persists, please contact GitHub Support, including the request ID 3C32:203416:1304F41:153BE2E:698F2D51. To retry, leave a comment on this pull request asking Copilot to try again.

I'm seeing it here:
https://github.com/mgifford/o-hat-scanner/pull/26

It would probably be better if there were only 2 issues added per half hour, rather than having a bunch of new PRs created all at once.

This should be working within the resource limits of GitHub.

I don't know what I'm supposed to do with this:
https://github.com/mgifford/o-hat-scanner/actions/runs/21989364482/job/63531926200

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

首先检查链接运行中的 GitHub Actions 作业,以及在 o-hat-scanner#26 创建 pull request 的工作流。重现 Copilot 请求激增的情况,并确定如何强制执行每半小时两个 issue 的拟议限制;当工作流保持在 GitHub 资源限制内且不触发 rate-limit 失败时,即视为完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
github-actions, typescript
领域
ci-cd, devops
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
30/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。