migrations_lockfile.txt 842 B

12345678910111213141516171819202122232425262728
  1. Django migrations lock file. This helps us avoid migration conflicts on master.
  2. If you have a conflict in this file, it means that someone has committed a migration
  3. ahead of you.
  4. To resolve this, rebase against latest master and regenerate your migration. This file
  5. will then be regenerated, and you should be able to merge without conflicts.
  6. explore: 0001_add_explore_saved_query_model
  7. feedback: 0004_index_together
  8. hybridcloud: 0019_add_provider_webhook_payload
  9. nodestore: 0002_nodestore_no_dictfield
  10. remote_subscriptions: 0003_drop_remote_subscription
  11. replays: 0004_index_together
  12. sentry: 0842_create_organization_member_invite_table
  13. social_auth: 0002_default_auto_field
  14. tempest: 0002_make_message_type_nullable
  15. uptime: 0031_translate_uptime_object_headers_to_lists_take_three
  16. workflow_engine: 0036_action_remove_legacy_fields