From 540a940eb30c1aaaad0b3b5ed64a52c90f59891b Mon Sep 17 00:00:00 2001 From: Rick Staa Date: Wed, 19 Aug 2026 14:13:33 +0200 Subject: [PATCH] ci: validate each example's on-chain overlay too The loop parses every compose.yml and stops there, so no compose.onchain.yml is checked by anything. That is the file nobody runs before merging, since it needs a wallet, an RPC and a keystore, and the one most likely to break. Interpolating .env.example also proves that file still lists every variable the overlay reads. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/lint.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml index 739c3a0..65d37ca 100644 --- a/.github/workflows/lint.yml +++ b/.github/workflows/lint.yml @@ -32,5 +32,12 @@ jobs: example=${dir%/} [ -f "$example/compose.yml" ] || continue docker compose -f "$example/compose.yml" config --quiet || status=1 + # The on-chain overlay is the one nobody runs before merging: it needs + # a wallet, an RPC and a keystore. Interpolating .env.example also + # proves that file still lists every variable the overlay reads. + [ -f "$example/compose.onchain.yml" ] || continue + docker compose --env-file "$example/.env.example" \ + -f "$example/compose.yml" -f "$example/compose.onchain.yml" \ + config --quiet || status=1 done exit $status