From 135a497d27d794030ef9a8fadef9f8dbe62116b1 Mon Sep 17 00:00:00 2001 From: Cristian Magherusan-Stanciu Date: Tue, 27 Oct 2026 19:50:43 +0100 Subject: [PATCH] docs(ci): an evicted migration ends the run cancelled, not green The migrate-aws concurrency comment said an evicted queued migration leaves the run green. A cancelled job makes the run conclude cancelled; the summary job still runs and prints the per-cloud results. Closes #201 Co-Authored-By: Claude Opus 5.5 --- .github/workflows/database-migration.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/database-migration.yml b/.github/workflows/database-migration.yml index 84850fcba..ed49679c9 100644 --- a/.github/workflows/database-migration.yml +++ b/.github/workflows/database-migration.yml @@ -267,9 +267,9 @@ jobs: # consequences, both accepted as better than concurrent writers to one # database: # - GitHub keeps one pending entry per group, so a queued migration can be - # evicted by a later dispatch. Unlike rollback.yml, the `summary` job - # below does not exit 1 on a non-success result, so an evicted migration - # leaves the run green; read the per-cloud results it prints. + # evicted by a later dispatch. The evicted job ends `cancelled`, so the + # run concludes `cancelled`, not green; the `summary` job (if: always()) + # still runs and prints the per-cloud results. # - if the `environment:` binding below carries required reviewers, it is # undocumented whether a job parked awaiting approval holds its group. concurrency: