forked from getsentry/sentry
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmigrations_lockfile.txt
More file actions
42 lines (23 loc) · 1.14 KB
/
migrations_lockfile.txt
File metadata and controls
42 lines (23 loc) · 1.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
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.
discover: 0003_discover_json_field
explore: 0006_add_changed_reason_field_explore
feedback: 0007_cleanup_failed_safe_deletes
flags: 0001_squashed_0004_add_flag_audit_log_provider_column
hybridcloud: 0024_add_project_distribution_scope
insights: 0002_backfill_team_starred
monitors: 0013_delete_monitor_is_muted_field
nodestore: 0001_squashed_0002_nodestore_no_dictfield
notifications: 0002_notificationmessage_jsonfield
preprod: 0019_add_tooling_version_fields
prevent: 0002_alter_integration_id_not_null
releases: 0004_cleanup_failed_safe_deletes
replays: 0007_organizationmember_replay_access
sentry: 1013_add_repositorysettings_table
social_auth: 0003_social_auth_json_field
tempest: 0003_use_encrypted_char_field
uptime: 0049_cleanup_failed_safe_deletes
workflow_engine: 0104_action_data_fallthrough_type