Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not update max_migration.txt when a merge migration is created. #78

Closed
tolomea opened this issue May 21, 2021 · 0 comments · Fixed by #361
Closed

Does not update max_migration.txt when a merge migration is created. #78

tolomea opened this issue May 21, 2021 · 0 comments · Fixed by #361

Comments

@tolomea
Copy link

tolomea commented May 21, 2021

Obviously I had to bypass the system checks to even get this to run.
We're not too concerned about having a linear history but would really like migration conflicts to be git conflicts.
I plan to encourage a move toward linear anyway by encouraging use of rebase, but the transition onto this tool would be easier if my team mates didn't have to go cold turkey on merges.
Incidentally it happens because in the underlying code --merge does not go through write_migration_files it calls MigrationWriter directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant