Remove old migration file

db/migrate/20170322070910_create_ci_scheduled_triggers.rb

-# See http://doc.gitlab.com/ce/development/migration_style_guide.html
-# for more information on how to write migrations for GitLab.
-
-class CreateCiScheduledTriggers < ActiveRecord::Migration
-  include Gitlab::Database::MigrationHelpers
-
-  # Set this constant to true if this migration requires downtime.
-  DOWNTIME = false
-
-  # When a migration requires downtime you **must** uncomment the following
-  # constant and define a short and easy to understand explanation as to why the
-  # migration requires downtime.
-  # DOWNTIME_REASON = ''
-
-  # When using the methods "add_concurrent_index" or "add_column_with_default"
-  # you must disable the use of transactions as these methods can not run in an
-  # existing transaction. When using "add_concurrent_index" make sure that this
-  # method is the _only_ method called in the migration, any other changes
-  # should go in a separate migration. This ensures that upon failure _only_ the
-  # index creation fails and can be retried or reverted easily.
-  #
-  # To disable transactions uncomment the following line and remove these
-  # comments:
-  # disable_ddl_transaction!
-
-  def change
-    create_table :ci_scheduled_triggers do |t|
-      t.integer "project_id"
-      t.datetime "deleted_at"
-      t.datetime "created_at"
-      t.datetime "updated_at"
-      t.integer "owner_id"
-      t.string "description"
-      t.string "cron"
-      t.string "cron_time_zone"
-      t.datetime "next_run_at"
-      t.datetime "last_run_at"
-      t.string "ref"
-    end
-
-    add_index :ci_scheduled_triggers, ["next_run_at"], name: "index_ci_scheduled_triggers_on_next_run_at", using: :btree
-    add_index :ci_scheduled_triggers, ["project_id"], name: "index_ci_scheduled_triggers_on_project_id", using: :btree
-    add_foreign_key :ci_scheduled_triggers, :users, column: :owner_id, on_delete: :cascade
-  end
-end