98bb435f42
Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file.
22 lines
912 B
Ruby
22 lines
912 B
Ruby
# rubocop:disable all
|
|
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class RemoveMainLanguageFromProjects < ActiveRecord::Migration
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# 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
|
|
remove_column :projects, :main_language
|
|
end
|
|
end
|