Peter Evans

Hi @marten-seemann Glad you are finding the action useful. I'll have a go at implementing this. I think it can be done quite easily by leveraging octokit's [retry](https://github.com/octokit/plugin-retry.js) plugin. The...

I've added the retry octokit plugin in a feature branch. The default settings are for it to retry up to 3 times, while respecting the `Retry-After` header. It would be...

Ah, I see where the problem is now. The abuse detection is kicking in when the branch is being pushed to the repository with `git push`, not the calls to...

@marten-seemann I've added logic to retry the `git push` command. Unfortunately, I don't think there is any way to see the `Retry-After` header from the git response, but I think...

@marten-seemann I'm periodically checking the runs [here](https://github.com/protocol/.github/actions) to see if there have been any retries during the "Deploy" workflow, but not seen any runs for a while. I'll wait until...

@marten-seemann Sure, no problem. I'm happy to wait until we can confirm that the PR changes work well.

@marten-seemann I've looked through all the runs and what is interesting this time is that none of them triggered abuse detection for `git push` of the PR branch, which was...

@marten-seemann Please could you let me know when you run another deployment. I would like to check if `403` error responses are being successfully retried.

@dontcallmedom Thanks. Good to know! It makes sense now why the message changed.

/test repository=peter-evans/create-pull-request ref=retry build=true > [Command run output][1] [1]: https://github.com/peter-evans/create-pull-request-tests/actions/runs/891346251