From 7e6e22970956315faf3dd50f0dcf4a0e57b044a9 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Sun, 4 Jun 2023 07:57:30 +0000 Subject: [PATCH] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- MIGRATIONS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MIGRATIONS.md b/MIGRATIONS.md index 83d07e27cf..decd9f0ed6 100644 --- a/MIGRATIONS.md +++ b/MIGRATIONS.md @@ -2,7 +2,7 @@ 1. Create a Django migration file without running it using `docker exec -it cl-django python manage.py makemigrations ` - Give the migration file a name of what it does. - - If the migration doesn't do anything (like, it just tweaks the `choices` parameter), give it a `_noop.py` suffix. + - If the migration doesn't do anything (like, it just tweaks the `choices` parameter), give it a `_noop.py` suffix. 2. Generate raw SQL for the migration you just made on the command line using `docker exec -it cl-django python sqlmigrate search `. 3. Copy and paste that into a `.sql` file right next to to the migration file that was generated (give the SQL file the same name as the migration file). 4. Tweak the raw SQL as needed to avoid the issues outlined below, if any.