migrations_lockfile.txt 562 B

123456789101112
  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: 0002_feedback_add_org_id_and_rename_event_id
  7. nodestore: 0002_nodestore_no_dictfield
  8. replays: 0003_add_size_to_recording_segment
  9. sentry: 0562_drop_xactor_actor_from_state
  10. social_auth: 0002_default_auto_field