0fc9f9d3e7
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
29 lines
1.3 KiB
Ruby
29 lines
1.3 KiB
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class RenameMergeWhenBuildSucceeds < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = true
|
|
|
|
# When a migration requires downtime you **must** uncomment the following
|
|
# constant and define a short and easy to understand explanation as to why the
|
|
# migration requires downtime.
|
|
DOWNTIME_REASON = 'Renaming the column merge_when_build_succeeds'
|
|
|
|
# When using the methods "add_concurrent_index" or "add_column_with_default"
|
|
# you must disable the use of transactions as these methods can not run in an
|
|
# existing transaction. When using "add_concurrent_index" make sure that this
|
|
# method is the _only_ method called in the migration, any other changes
|
|
# should go in a separate migration. This ensures that upon failure _only_ the
|
|
# index creation fails and can be retried or reverted easily.
|
|
#
|
|
# To disable transactions uncomment the following line and remove these
|
|
# comments:
|
|
# disable_ddl_transaction!
|
|
|
|
def change
|
|
rename_column :merge_requests, :merge_when_build_succeeds, :merge_when_pipeline_succeeds
|
|
end
|
|
end
|