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.

admin: 0002_logentry_remove_auto_add
auth: 0008_alter_user_username_max_length
contenttypes: 0002_remove_content_type_name
jira_ac: 0001_initial
nodestore: 0001_initial
sentry: 0103_project_has_alert_filters
sessions: 0001_initial
sites: 0002_alter_domain_unique
social_auth: 0001_initial