migrations_lockfile.txt 632 B

12345678910111213141516
  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. admin: 0002_logentry_remove_auto_add
  7. auth: 0008_alter_user_username_max_length
  8. contenttypes: 0002_remove_content_type_name
  9. jira_ac: 0001_initial
  10. nodestore: 0001_initial
  11. sentry: 0102_collect_relay_analytics
  12. sessions: 0001_initial
  13. sites: 0002_alter_domain_unique
  14. social_auth: 0001_initial