sentry/migrations_lockfile.txt

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: 0019_add_provider_webhook_payload

nodestore: 0002_nodestore_no_dictfield

remote_subscriptions: 0003_drop_remote_subscription

replays: 0004_index_together

sentry: 0839_add_visibility_column_to_groupsearchview

social_auth: 0002_default_auto_field

tempest: 0002_make_message_type_nullable

uptime: 0029_uptime_subscription_index_domain_cols

workflow_engine: 0034_action_cleanup_1