step/job retry for flaky checks (merge queue) before failing required checks” #189451
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Product Feedback
What GitHub Actions topic or product is this about?
Workflow Configuration
Discussion Details
We use GitHub Actions together with the merge queue. Occasionally, an E2E test is flaky and fails transiently, which causes the required check to fail and the whole pull request to be removed from the merge queue.
It would be very helpful to have a first-class retry option in the workflow configuration (for a job and/or step) so that transient failures can be retried automatically within the same check run, and the check only concludes as failed after the retry limit is exceeded.
Additionally, we’d like a way to react inside the workflow when a retry occurs, similar to existing conditional handling for outcomes like
failureorcancelled. For example, we want to be able to create a Jira ticket and/or post a Slack message when retries happen, including metadata such as how many retries were needed before the run became green (or before it ultimately failed).Beta Was this translation helpful? Give feedback.
All reactions