Closed ReenigneArcher closed 1 year ago
@ReenigneArcher sorry for the late response.
I already had issue with PR creation API in the past and already did retry there -> https://github.com/derberg/copy-files-to-other-repositories/blob/main/lib/api-calls.js#L157
So as you can see there are already 5 retires and 5sec delay before each. The problem is not solvable with more retires and larger delays. It is not a rate limit, at least I haven't found in the past the answer to that issue. Maybe it is kind of DDoS prevention or something. Dunno 🤷🏼
I'm afraid the only solution is to not do parallel execution really.
Side question is, why do you need this parallel execution? We you care so much on the speed of the action? Maybe issues you have I already solved in AsyncAPI, the project where we use this action on over 60 repos.
Side question is, why do you need this parallel execution?
I don't necessarily need it, just speeds up the workflow a bit as I have 6 scenarios. Not a big deal at all. I would be much happier to see #24 addressed. If a rebase could be done to a specified branch instead of opening multiple PRs, I think this action would be nearly perfect. It's okay if you want to close this. Thanks for all your efforts!
yeah #24 is tricky.
I'll close this one then as GitHub is really mysterious on this error. There is no clean solution for now
Describe the bug
A clear and concise description of what the bug is.
Sometimes when running this action, I get rate limited. I already have set the matrix to only 2 parallel jobs. I will switch to 1, but it would be nice if the action had a retry option to try again after a certain number of seconds or something.
How to Reproduce
Steps to reproduce the issue. Attach all resources that can help us understand the issue:
Expected behavior
A clear and concise description of what you expected to happen.
Auto retry to recreate PRs if rate limited.