gitlab-org--gitlab-foss/db/migrate/20171211145425_add_can_push...

class AddCanPushToDeployKeysProjects < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  # Set this constant to true if this migration requires downtime.
  DOWNTIME = false
  disable_ddl_transaction!

  def up
    add_column_with_default :deploy_keys_projects, :can_push, :boolean, default: false, allow_null: false
  end

  def down
    remove_column :deploy_keys_projects, :can_push
  end
end
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 AddCanPushToDeployKeysProjects < ActiveRecord::Migration[4.2]`
Merge branch 'sh-migrate-can-push-to-deploy-keys-projects-10-3' into 'security-10-3' [10.3] Migrate `can_push` column from `keys` to `deploy_keys_project` See merge request gitlab/gitlabhq!2276 (cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c) 1f2bd3c0 Backport to 10.3 2018-01-05 15:23:44 +00:00			`include Gitlab::Database::MigrationHelpers`

			`# Set this constant to true if this migration requires downtime.`
			`DOWNTIME = false`
			`disable_ddl_transaction!`

			`def up`
			`add_column_with_default :deploy_keys_projects, :can_push, :boolean, default: false, allow_null: false`
			`end`

			`def down`
			`remove_column :deploy_keys_projects, :can_push`
			`end`
			`end`