Add a start flag, and let --check survive a first deploy

-e start=false (mode sync in CI) lands the payload and starts nothing, for
migrations. A check run on a never-deployed stack now skips Compose with a note
instead of failing on the missing directory.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Lucas Winther
2026-09-30 15:04:56 +02:00
co-authored by Claude Opus 5.5
parent c9a4d56851
commit 78b227f32d
12 changed files with 151 additions and 14 deletions
+9 -2
View File
@@ -30,12 +30,15 @@ on:
- webapp
- webapp-staging
mode:
description: check reports what would change; deploy does it
description: >-
check reports what would change; sync copies the files but starts
nothing; deploy does both
required: true
default: check
type: choice
options:
- check
- sync
- deploy
pull:
description: >-
@@ -96,7 +99,7 @@ jobs:
''|*[!a-z0-9_-]*) echo "refusing STACK='$STACK'"; exit 1 ;;
esac
case "$MODE" in
check|deploy) ;;
check|sync|deploy) ;;
*) echo "refusing MODE='$MODE'"; exit 1 ;;
esac
# An unchecked value can smuggle extra `-e` overrides onto the command
@@ -145,6 +148,10 @@ jobs:
# with no error message and a green-looking cancel.
if [ "$MODE" = "check" ]; then
set -- --check --diff
elif [ "$MODE" = "sync" ]; then
# A real run that stops before Compose: the payload lands, the
# directories and networks are created, no container is touched.
set -- -e start=false
else
set --
fi