From 32b384ca30aa04184efbf83ce33143ae052cde6b Mon Sep 17 00:00:00 2001 From: Thomas Berdy Date: Fri, 27 Mar 2026 18:56:50 +0100 Subject: [PATCH] docs: detail available conditions for Auto-Retry rules Document all condition attributes (job name, pipeline name, repository, branch, conclusion, flaky, log pattern) so users know what filtering options are available when configuring retry rules. Co-Authored-By: Claude Opus 4.6 (1M context) Change-Id: Iafe75d77734dc92d7496030d24e346a6efed9d1d Claude-Session-Id: 67e259e5-08dc-453d-ab2b-ae121f93a2db --- src/content/docs/ci-insights/auto-retry.mdx | 34 +++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/src/content/docs/ci-insights/auto-retry.mdx b/src/content/docs/ci-insights/auto-retry.mdx index b37b32e9a9..76a9966b97 100644 --- a/src/content/docs/ci-insights/auto-retry.mdx +++ b/src/content/docs/ci-insights/auto-retry.mdx @@ -80,3 +80,37 @@ failures. Each rule specifies: - **Retry mode**: The mode of retry, either retrying all failed jobs (`job`) or the entire workflow (`pipeline`) + +### Conditions + +Conditions let you control which job failures should trigger a retry. Each +condition matches against a specific attribute of the failed job. You can +combine multiple conditions in a single rule — all conditions must match for +the rule to apply. + +The following condition attributes are available: + +- **Job name**: Match against the name of the failed job. This allows you to + target retries to specific jobs known to be flaky. + +- **Pipeline name**: Match against the name of the workflow (pipeline) that + contains the failed job. + +- **Repository**: Restrict the rule to specific repositories. + +- **Branch**: Restrict the rule to specific branches. You can also enter custom + branch names that are not yet in the list. + +- **Conclusion**: Match against the type of failure. Available values are + `failure` (the job failed) and `timed_out` (the job exceeded its time limit). + +- **Flaky**: Match against whether Mergify has detected the job as flaky. + Set to `true` to only retry jobs that have been identified as flaky, or + `false` to only retry jobs that are not considered flaky. + +- **Log pattern**: Match against the content of the job logs and GitHub + Actions check-run annotations using regular expressions. Each pattern is + evaluated against individual log lines. You can specify multiple + patterns — a retry is triggered if any of the patterns match. For + example, `timeout|connection refused` would match any log line + containing either "timeout" or "connection refused". \ No newline at end of file