-
Notifications
You must be signed in to change notification settings - Fork 159
feat(*): add multi retry strategy #700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: lsytj0413 <[email protected]>
Thanks for the PR! Think we need little time to think about this. Personally must say I'm not a big fan of per-error retry policies. I think its confusing as it makes it impossible to figure out when next retry is going to happen. Also imo very hard to implement and third its quite confusing. I'd really like to see some real life use cases where this is needed. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/remove-stale |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@lsytj0413 First of all, many thanks for your PR! Second, I added the Please feel free to contribute, here or on referenced issue. |
Signed-off-by: lsytj0413 [email protected]
Many thanks for submitting your Pull Request ❤️!
Please specify parts of this PR update:
Discussion or Issue link:
What this PR does / why we need it:
Add multi retry strategy to an action.
Special notes for reviewers:
Additional information:
Fixed #681