https://github.com/dharmit/migrations
Understanding django migrations
https://github.com/dharmit/migrations
Last synced: 11 months ago
JSON representation
Understanding django migrations
- Host: GitHub
- URL: https://github.com/dharmit/migrations
- Owner: dharmit
- Created: 2015-05-06T08:40:18.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2015-05-06T09:43:39.000Z (about 11 years ago)
- Last Synced: 2025-02-10T05:41:46.116Z (over 1 year ago)
- Language: Python
- Homepage:
- Size: 129 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Django Migrations
=================
* This is a placeholder repository for understanding django migrations.
* Assume there are three branches `stage`, `dev1` and `dev2`.
* Code is being written in the latter two branches only.
* We can follow below workflow for consistent migrations:
1. Migrations created in one branch (say, `dev1`) can be merged into `stage`.
2. Developer working on `dev2` branch might have some migrations in her branch. But when she rebases `dev2` with `stage`, migrations applied in `dev1` get pulled in.
3. `dev2` can run `python manage.py makemigrations`. If there are migration conflicts, django will compplain about it and suggest you to do `python manage.py makemigations --merge`. Do the same.