migrations_lockfile.txt 674 B

123456789101112131415
  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. feedback: 0004_index_together
  7. hybridcloud: 0016_add_control_cacheversion
  8. nodestore: 0002_nodestore_no_dictfield
  9. remote_subscriptions: 0002_remove_separate_remote_subscription
  10. replays: 0004_index_together
  11. sentry: 0731_add_insight_project_flags
  12. social_auth: 0002_default_auto_field
  13. uptime: 0002_remove_separate_remote_subscription