You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this should be classified as an enhancement rather than a bug/feature.
Summary
I propose enhancing the retry mechanism to allow it to trigger automatically when submitting pull requests.
Motivation
This enhancement is necessary to improve the testing process and ensure that developers can easily rerun workflows when facing transient issues during PR submissions. It benefits the project by increasing the reliability of CI/CD pipelines.
Describe the Solution You'd Like
Implement a workflow that automatically triggers retries based on the workflow_run event. This would replace the current manual invocation of rerun workflows and eliminate permission issues that hinder the retry mechanism.
Describe Alternatives You've Considered
I considered keeping the existing manual retry mechanism, but it does not address the permission issues and is less user-friendly. The proposed solution offers a more streamlined approach.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Summary
I propose enhancing the retry mechanism to allow it to trigger automatically when submitting pull requests.
Motivation
This enhancement is necessary to improve the testing process and ensure that developers can easily rerun workflows when facing transient issues during PR submissions. It benefits the project by increasing the reliability of CI/CD pipelines.
Describe the Solution You'd Like
Implement a workflow that automatically triggers retries based on the workflow_run event. This would replace the current manual invocation of rerun workflows and eliminate permission issues that hinder the retry mechanism.
Describe Alternatives You've Considered
I considered keeping the existing manual retry mechanism, but it does not address the permission issues and is less user-friendly. The proposed solution offers a more streamlined approach.
Additional Context
No response
The text was updated successfully, but these errors were encountered: