Chris Parsons adde69a922 Run database migrations on deploy before starting container ... Migrations were never being run against production on deploy, causing schema mismatches when new columns are added. This adds a migration step using the PROD_DATABASE_URL secret before bringing up the new container, with set -e to abort the deploy if migrations fail. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-04-06 02:48:44 +00:00
..
deploy.yml	Run database migrations on deploy before starting container	2026-04-06 02:48:44 +00:00
label-subissues.yaml	Create label-subissues.yaml	2026-03-10 13:40:44 -07:00