merging migrations

migrations_lockfile.txt

@@ -9,4 +9,5 @@ nodestore: 0002_nodestore_no_dictfield
 sentry: 0508_index_checkin_monitorenvironment
 sentry: 0507_delete_pending_deletion_rules
 sentry: 0507_add_oidc_scopes
+sentry: 0508_merging_migrations
 social_auth: 0001_initial

src/sentry/migrations/0508_merging_migrations.py

@@ -0,0 +1,24 @@
+# Generated by Django 2.2.28 on 2023-07-10 20:12
+
+from sentry.new_migrations.migrations import CheckedMigration
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production. For
+    # the most part, this should only be used for operations where it's safe to run the migration
+    # after your code has deployed. So this should not be used for most operations that alter the
+    # schema of a table.
+    # Here are some things that make sense to mark as dangerous:
+    # - Large data migrations. Typically we want these to be run manually by ops so that they can
+    #   be monitored and not block the deploy for a long period of time while they run.
+    # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
+    #   have ops run this and not block the deploy. Note that while adding an index is a schema
+    #   change, it's completely safe to run the operation after the code has deployed.
+    is_dangerous = False
+
+    dependencies = [
+        ("sentry", "0507_delete_pending_deletion_rules"),
+        ("sentry", "0507_add_oidc_scopes"),
+    ]
+
+    operations = []