Pull request creation failed. Validation failed: was submitted too quickly.

huangapple go评论62阅读模式
英文:

Pull request creation failed. Validation failed: was submitted too quickly

问题

我正在尝试创建一个拉取请求,但一直出现这个错误。

我一直在尝试创建这个PR,但它不起作用。我不知道问题出在哪里,我还尝试通过在git中编写命令来创建这个PR并将其推送到我的源仓库。

英文:

Pull request creation failed. Validation failed: was submitted too quickly.

I'm trying to create a pull request, but this error keeps showing up.

I'm constantly trying to make this PR, but it's not working. I don't know where the problem is, I'm also trying by writing commands in git to make this PR and push it into my origin repository.

答案1

得分: 1

GitHub 在其平台上面临着前所未有的垃圾邮件和滥用问题。人们试图通过自动拉取请求来潜入安全漏洞,部署比特币挖矿程序在 GitHub 操作中,接管他人的 GitHub CodeSpaces,获取发布到包管理站点(如 npm 和 nuget)的凭据,以及许多其他问题。

为了应对这种滥用行为,GitHub 实施了一些已记录和未记录的速率限制。主要是为了防止自动化程序一次性滥发数百个存储库。

有许多权衡因素,比如特定用户发出的请求数量。但也包括 IP 地址。还有一些未记录的元素,我在这里进行了推测,比如您当前的位置、帐户年龄和您的一般“地位”。

如果您受到速率限制的影响,您可以通过 REST 调用 API 请求公共速率限制的状态GraphQL 的类似 API。这应该告诉您当前剩余的调用数量以及何时重置这些值。

如果您受到未记录的(或所谓的第二级速率限制)的影响,那么没有办法轻松地检查原因。这是为了防止不良行为者准确了解暂时禁止他们的原因。

在大多数情况下,速率限制在一个小时后完全重置。

如果您需要更高的速率限制,GitHub 企业客户可以获得更高的数字

英文:

GitHub is facing an unprecedented amount of spam and abuse on its platform. People try sneaking in security bugs in automated pull-requests, deploy bitcoin miners on GitHub actions, take over people's GitHub CodeSpaces, gain access to credentials to publish to package management sites, like npm and nuget and so much more.

To combat this abuse, GitHub has a number of documented and undocumented rate limits in place. Mostly these are there to prevent automation from automatically spamming 100s of repos at once.

A number of factors are weighed in, like the number of requests made by a specific user. But also the IP address. But also a number of undocumented elements, and I'm speculating here, things like your current location, account age and your general "standing".

If you are hit by a rate limit, you can request the status of your public rate limits through the API fo REST calls and a similar API for GraphQL. That should tell you the current number of remaining calls and when there values will reset.

If you're hit by an undocumented (or so-called 2nd level rate limit), then there is no way to easily check the reason. This is to prevent bad actors from knowing exactly what's getting them temporarily banned.

In most cases rate limits reset completely after an hour.

If you need higher rate limits, there are higher numbers available to GitHub Enterprise clients.

huangapple
  • 本文由 发表于 2023年6月13日 13:54:19
  • 转载请务必保留本文链接:https://go.coder-hub.com/76462012.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定