gitlab-org--gitlab-foss/db/migrate/20160222153918_create_appearances_ce.rb

# rubocop:disable all
class CreateAppearancesCe < ActiveRecord::Migration[4.2]
  def change
    unless table_exists?(:appearances)
      create_table :appearances do |t|
        t.string :title
        t.text :description
        t.string :header_logo
        t.string :logo

        t.timestamps null: false
      end
    end
  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 CreateAppearancesCe < ActiveRecord::Migration[4.2]`
Branded login page also in CE The only major difference with the EE version is the change from a light and dark logo to only a header logo The dark logo wasn't used anyway, so it seemed to make sense to me to rename the field to the actual function of it 2016-02-22 14:49:16 -05:00			`def change`
			`unless table_exists?(:appearances)`
			`create_table :appearances do \|t\|`
			`t.string :title`
			`t.text :description`
			`t.string :header_logo`
			`t.string :logo`

			`t.timestamps null: false`
			`end`
			`end`
			`end`
			`end`