chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs: add Alembic sequential migration numbering rule to CLAUDE.md (#38)

Browse Source 
Migrations must use sequential numbered prefixes (e.g., 040_desc.py) with
--rev-id flag. Never use auto-generated revision IDs. Updated both the
lessons learned section and the development commands.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
chihlasm
2026-03-01 14:53:05 -05:00
parent 9811c56280
commit e25f041332
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CLAUDE.md
View File

@@ -166,7 +166,7 @@ cd frontend && npm run build
# Database migrations
cd backend && alembic upgrade head
alembic revision --autogenerate -m "Description"
alembic revision --autogenerate -m "Description" --rev-id=NNN # NNN = next sequential number
# Access PostgreSQL
docker exec -it patherly_postgres psql -U postgres -d patherly
@@ -304,6 +304,8 @@ navigate(`/trees/${newTree.id}/edit`)
**37. First deployed user needs manual admin promotion:** New users default to `engineer` role. Promote via SQL: `UPDATE users SET role = 'admin' WHERE email = '...';` then re-login for new JWT.
**38. Alembic migrations MUST use sequential numbered prefixes:** Check `backend/alembic/versions/` for the highest numbered migration and use the next number. Format: `XXX_descriptive_name.py` (e.g., `040_add_whatever.py`). NEVER use auto-generated revision IDs like `0f1ca2af3647`. Always pass `--rev-id` flag: `alembic revision --autogenerate -m "desc" --rev-id=040`.
---
## RBAC & Permissions