Fix: Merge the two current heads in Alembic. #113
Conversation
| @@ -0,0 +1,27 @@ | |||
| """Merge heads | |||
There was a problem hiding this comment.
Are you merging this by hand? As it stands this does nothing so there is no reason to even keep it?
There was a problem hiding this comment.
No, this is generated from the CLI using alembic merge heads. Currently, we have two branches in Alembic. This just merges the two branches together from Alembic's perspective, but doesn't actually change the DB. It's clean-up of some Alembic mess (multiple heads), not deep changes. We need to keep it (and you need to run alembic update head) so that future migrations get built on this merge, instead of creating more branches.
There was a problem hiding this comment.
After you run this, I'm curious to see what a alembic revision --autogenerate -m "Update to current db structure" produces for you. It does create some operations for me, but perhaps my db is missing something?
There was a problem hiding this comment.
OK, is this ready to merge then?
|
Yes, I'll send more PRs after this is merged. |
|
Given the failing tests, you'll have to merge this -- I don't have access to push. |
No description provided.