gitlab-org--gitlab-foss/db/migrate/20160421130527_disable_repo...

# rubocop:disable all
class DisableRepositoryChecks < ActiveRecord::Migration[4.2]
  def up
    change_column_default :application_settings, :repository_checks_enabled, false 
    execute 'UPDATE application_settings SET repository_checks_enabled = false'
  end

  def down
    change_column_default :application_settings, :repository_checks_enabled, true    
    execute 'UPDATE application_settings SET repository_checks_enabled = true'
  end
end
Enable RuboCop for migrations 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. 2016-06-09 12:39:16 +00:00			`# rubocop:disable all`
Add version 4.2 to all existing migrations 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 2018-11-13 07:27:31 +00:00			`class DisableRepositoryChecks < ActiveRecord::Migration[4.2]`
Disable 'repository check' feature in 8.7.0 It still causes too many false alarms. 2016-04-21 14:50:26 +00:00			`def up`
			`change_column_default :application_settings, :repository_checks_enabled, false`
			`execute 'UPDATE application_settings SET repository_checks_enabled = false'`
			`end`

			`def down`
			`change_column_default :application_settings, :repository_checks_enabled, true`
			`execute 'UPDATE application_settings SET repository_checks_enabled = true'`
			`end`
			`end`