gitlab-org--gitlab-foss/db/migrate/20130711063759_create_proje...

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

  def change
    create_table :project_group_links do |t|
      t.integer :project_id, null: false
      t.integer :group_id, null: false

      t.timestamps null: true
    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 12:39:16 +00:00			`# rubocop:disable all`
Bring ProjectGroupLink model and migrations from EE Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2016-03-11 16:47:05 +00:00			`class CreateProjectGroupLinks < ActiveRecord::Migration`
Make the downtime_check task happy Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-30 15:15:02 +00:00			`DOWNTIME = false`

Bring ProjectGroupLink model and migrations from EE Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2016-03-11 16:47:05 +00:00			`def change`
			`create_table :project_group_links do \|t\|`
			`t.integer :project_id, null: false`
			`t.integer :group_id, null: false`

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 15:45:08 +00:00			`t.timestamps null: true`
Bring ProjectGroupLink model and migrations from EE Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2016-03-11 16:47:05 +00:00			`end`
			`end`
			`end`