diff options
| author | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-14 09:27:19 +0300 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2026-05-14 06:45:22 +0000 |
| commit | 003b219da51dceaaccc787cb804b5ea7cdb782d6 (patch) | |
| tree | 4e9cc95e44ee9d09cd02d6908e182f041404fafe /scripts | |
| parent | f00fe5618d4693d83047fab9cc135cf97d1db109 (diff) | |
| download | vyos-documentation-003b219da51dceaaccc787cb804b5ea7cdb782d6.tar.gz vyos-documentation-003b219da51dceaaccc787cb804b5ea7cdb782d6.zip | |
ci(ai-validation): skip prepare on Mergify-authored PRs
Lifts the existing Mergify-author short-circuit (today inside validate's
`secrets-check` step) to a job-level `if:` on `prepare`, so the whole
pipeline skips for backport/queue PRs.
Why now: every Mergify backport whose merge ref shares no shallow
ancestor with the (advanced) base branch fails the prepare step at
git diff "$BASE...HEAD" --name-only ...
fatal: FETCH_HEAD...HEAD: no merge base
(because base is `git fetch --no-tags --depth=1` and the merge ref is
`fetch-depth: 2`). Proximate symptom: run 25842928620 on PR #2042
(sagitta backport of #2023). AI Validation isn't a required check so
the queue isn't blocked, but every Mergify backport is left with a red
"prepare" check that adds noise to PR review.
The validate-level skip in commit 0e8a2956 was correct for the
"claude-code-action rejects bot-initiated runs" failure mode but
fires too late — prepare has already run and crashed before validate's
`if: needs.prepare.outputs.has_md_changes == 'true'` even evaluates.
Implementation: single job-level `if:` on prepare. validate's
`needs: [prepare]` cascades the skip naturally (skipped needs make
the dependent's expression-based `if:` evaluate against empty outputs).
The in-step author check in validate stays as defense-in-depth.
🤖 Generated by [robots](https://vyos.io)
(cherry picked from commit 7d94d6116be1a4776b7317cb5190a83dd065e571)
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
