1 files changed, 0 insertions, 38 deletions
diff --git a/db/migrate/20171229225929_change_user_project_limit_not_null_and_remove_default.rb b/db/migrate/20171229225929_change_user_project_limit_not_null_and_remove_default.rb
deleted file mode 100644
index b9efdb8bb8f..00000000000
--- a/db/migrate/20171229225929_change_user_project_limit_not_null_and_remove_default.rb
+++ /dev/null
@@ -1,38 +0,0 @@
-# See http://doc.gitlab.com/ce/development/migration_style_guide.html
-# for more information on how to write migrations for GitLab.
-
-class ChangeUserProjectLimitNotNullAndRemoveDefault < ActiveRecord::Migration[4.2]
-  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", "remove_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" or "remove_concurrent_index" methods make sure
-  # that either of them 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 or removing fails
-  # and can be retried or reverted easily.
-  #
-  # To disable transactions uncomment the following line and remove these
-  # comments:
-  # disable_ddl_transaction!
-
-  def up
-    # Set Users#projects_limit to NOT NULL and remove the default value
-    change_column_null :users, :projects_limit, false
-    change_column_default :users, :projects_limit, nil
-  end
-
-  def down
-    change_column_null :users, :projects_limit, true
-    change_column_default :users, :projects_limit, 10
-  end
-end