| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Squash old migrations | Nick Thomas | 2019-07-02 | 1 | -7/+0 |
| | | | | | Use the `squasher` gem to squash migrations older than the start of 2018 | ||||
| * | Add version 4.2 to all existing migrationsjprovazn-versioned-migrations | Jan Provaznik | 2018-11-22 | 1 | -1/+1 |
| | | | | | | | | | | 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 | ||||
| * | Add specs for ProjectDestroyWorker | Tiago Botelho | 2017-07-20 | 1 | -24/+0 |
| | | |||||
| * | Handle errors while a project is being deleted asynchronously. | Timothy Andrew | 2017-07-20 | 1 | -0/+31 |
| 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. | |||||
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |