GitHub rate limit triggered when syncing a lot of repositories

🐞 Describe the bug

When executing the repo-file-sync-action in my workflow, it shows as successfully having completed but the logs show multiple instances of the following error:

Error: You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.

Each time this error is reported, the PR fails to be created. For example:

Repository Info
Slug		: jellyfish-queue
Owner		: product-os
Https Url	: https://github.com/product-os/jellyfish-queue
Branch		: default
	
Locally syncing file(s) between source and target repository
Pushing changes to target repository
Creating new PR
Error: You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.
Error: HttpError: You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.

No PR is created on the jellyfish-queue repo.

📚 To Reproduce

Create a sync.yml file that should result in PRs being created on a lot (about 20) of repos.

💡 Expected behavior

No errors logged, all expected PRs successfully created.

🖼️ Screenshots

N/A

⚙️ Environment

• Action version: 1.7.0

📋 Additional context

I’m not sure if this means the GitHub user associated with GH_PAT has been rate-limited or whether repo-file-sync-action or the workflow itself has been rate-limited?

Either way, I wonder if it would help to add a RATE_LIMIT option or similar that could be used to throttle the action’s requests to the GitHub API to mitigate this error?

[BetaHuhn]

Great, I will merge it into master and release a new version!

[grahammcculloch]

@BetaHuhn no problems running with the develop branch - although I can’t prove that it hit the rate limit and backed off 😃