| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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 cop for use of remove_columnadd-remove-column-cop | Sean McGivern | 2017-12-11 | 1 | -0/+1 |
| | | | | | | | | remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration. | ||||
| * | Split migration to create label priorities | Douglas Barbosa Alexandre | 2016-10-19 | 1 | -0/+17 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |