12345678910111213141516 |
- Django migrations lock file. This helps us avoid migration conflicts on master.
- If you have a conflict in this file, it means that someone has committed a migration
- ahead of you.
- To resolve this, rebase against latest master and regenerate your migration. This file
- will then be regenerated, and you should be able to merge without conflicts.
- feedback: 0004_index_together
- hybridcloud: 0017_add_billing_role
- nodestore: 0002_nodestore_no_dictfield
- remote_subscriptions: 0003_drop_remote_subscription
- replays: 0004_index_together
- sentry: 0792_add_billing_role
- social_auth: 0002_default_auto_field
- uptime: 0018_add_trace_sampling_field_to_uptime
- workflow_engine: 0012_data_source_type_change
|