d3d9077830
This works the same way as change_column_type_using_background_migration, but for renaming a column. It takes a table, not a relation, to match its concurrent counterpart. Also, generalise the cleanup migrations to reduce code duplication. |
||
|---|---|---|
| .. | ||
| api | ||
| backup | ||
| banzai | ||
| bitbucket | ||
| constraints | ||
| container_registry | ||
| gitaly | ||
| gitlab | ||
| google_api | ||
| json_web_token | ||
| mattermost | ||
| microsoft_teams | ||
| object_storage | ||
| omni_auth/strategies | ||
| rspec_flaky | ||
| system_check | ||
| additional_email_headers_interceptor_spec.rb | ||
| after_commit_queue_spec.rb | ||
| disable_email_interceptor_spec.rb | ||
| event_filter_spec.rb | ||
| expand_variables_spec.rb | ||
| extracts_path_spec.rb | ||
| feature_spec.rb | ||
| file_size_validator_spec.rb | ||
| forever_spec.rb | ||
| gitlab_spec.rb | ||
| milestone_array_spec.rb | ||
| system_check_spec.rb | ||
| uploaded_file_spec.rb | ||