- 22 Nov, 2018 1 commit
-
-
Jan Provaznik authored
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
-
- 20 Jul, 2017 2 commits
-
-
Tiago Botelho authored
-
Timothy Andrew authored
1. Rescue all errors that `Projects::DestroyService` might throw, to prevent the worker from leaving things in an inconsistent state 2. Unmark the project as `pending_delete` 3. Add a `delete_error` text column to `projects`, and save the error message in there, to be shown to the project masters/owners.
-
- 16 May, 2017 1 commit
-
-
Valery Sizov authored
-
- 04 May, 2017 1 commit
-
-
Luke "Jared" Bennett authored
-
- 06 Apr, 2017 1 commit
-
-
blackst0ne authored
-
- 20 Jul, 2016 1 commit
-
-
Yorick Peterse authored
These new checks can be used to check if migrations require downtime or not (as tagged by their authors). In CI this compares the current branch with master so migrations added by merge requests are automatically verified. To check the migrations added since a Git reference simply run: bundle exec rake gitlab:db:downtime_check[GIT_REF]
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 19 May, 2016 2 commits
-
-
Yorick Peterse authored
Since we eager load everything in lib/ putting ERB code in .rb files will result in syntax errors. By moving the templates to ./generator_templates we can work around this.
-
Yorick Peterse authored
-
- 12 May, 2016 2 commits
-
-
Yorick Peterse authored
-
Yorick Peterse authored
This allows us to automatically include Gitlab::Database::MigrationHelpers into newly generated migrations.
-