gitlab-org--gitlab-foss/db/migrate/20151105094515_create_releases.rb

# rubocop:disable all
class CreateReleases < ActiveRecord::Migration
  DOWNTIME = false

  def change
    create_table :releases do |t|
      t.string :tag
      t.text :description
      t.integer :project_id

      t.timestamps null: true
    end

    add_index :releases, :project_id
    add_index :releases, [:project_id, :tag]
  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 release model Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2015-11-05 05:03:02 -05:00			`class CreateReleases < ActiveRecord::Migration`
Make the downtime_check task happy Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-30 10:15:02 -05:00			`DOWNTIME = false`

Add release model Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2015-11-05 05:03:02 -05:00			`def change`
			`create_table :releases do \|t\|`
			`t.string :tag`
			`t.text :description`
			`t.integer :project_id`

Add `null: true` to timestamps in migrations that does not define it This is to ensure that migrations will still be consitent when we will upgrade to Rails 5 which default to `null: false` for timestamps columns. Fixes #23666. Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-28 10:45:08 -05:00			`t.timestamps null: true`
Add release model Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2015-11-05 05:03:02 -05:00			`end`

			`add_index :releases, :project_id`
			`add_index :releases, [:project_id, :tag]`
			`end`
			`end`