gitlab-org--gitlab-foss/db/migrate/20160225090018_add_delete_at_to_issues.rb

# rubocop:disable all
class AddDeleteAtToIssues < ActiveRecord::Migration[4.2]
  def change
    add_column :issues, :deleted_at, :datetime
    add_index :issues, :deleted_at
  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 08:39:16 -04: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 02:27:31 -05:00			`class AddDeleteAtToIssues < ActiveRecord::Migration[4.2]`
Soft delete issuables 2016-02-26 03:55:43 -05:00			`def change`
			`add_column :issues, :deleted_at, :datetime`
			`add_index :issues, :deleted_at`
			`end`
			`end`