Chris Parsons 89d52cca5e Run database migrations on deploy before starting container (#264) ... 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-05 22:50:23 -04:00
..
deploy.yml	Run database migrations on deploy before starting container (#264)	2026-04-05 22:50:23 -04:00
label-subissues.yaml	Create label-subissues.yaml	2026-03-10 13:40:44 -07:00