Skip to content
This repository was archived by the owner on Aug 30, 2026. It is now read-only.

Fix db-reset workflow: add missing --reset flag - #111

Merged
anth-volk merged 2 commits into
mainfrom
fix/fix-deploy-errors
Mar 10, 2026
Merged

anth-volk merged 2 commits into
mainfrom
fix/fix-deploy-errors

Conversation

@anth-volk

Copy link
Copy Markdown
Contributor

Fixes #110

Summary

  • Add --reset flag to scripts/init.py invocation in db-reset.yml
  • Without it, init.py skips dropping existing tables, and Alembic fails with relation "dynamics" already exists

Test plan

  • Re-run the "Reset production database" workflow after merging
  • Verify tables are dropped and recreated cleanly
  • Verify seeding completes successfully

🤖 Generated with Claude Code

anth-volk and others added 2 commits March 10, 2026 19:05
Without --reset, init.py takes the idempotent path and skips dropping
existing tables. Alembic then fails with "relation already exists"
because the tables were created outside of Alembic but alembic_version
was never populated.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@anth-volk
anth-volk marked this pull request as ready for review March 10, 2026 18:23
@anth-volk
anth-volk merged commit 80d68b3 into main Mar 10, 2026
5 checks passed
@anth-volk
anth-volk deleted the fix/fix-deploy-errors branch March 10, 2026 18:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

db-reset workflow fails: missing --reset flag causes 'relation already exists'

1 participant