summaryrefslogtreecommitdiff
path: root/db/migrate/20151105094515_create_releases.rb
Commit message (Collapse)AuthorAgeFilesLines
* Squash old migrationsNick Thomas2019-07-021-17/+0
| | | | Use the `squasher` gem to squash migrations older than the start of 2018
* Add version 4.2 to all existing migrationsjprovazn-versioned-migrationsJan Provaznik2018-11-221-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
* Make the downtime_check task happyfix-migrationsRémy Coutable2016-11-301-0/+2
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Add `null: true` to timestamps in migrations that does not define it23666-set-null-true-for-timestamps-columns-in-migrationsRémy Coutable2016-11-281-1/+1
| | | | | | | | | | This is to ensure that migrations will still be consitent when we will upgrade to Rails 5 which default to `null: false` for timestamps columns. Fixes #23666. Signed-off-by: Rémy Coutable <remy@rymai.me>
* Enable RuboCop for migrationsenable-rubocop-for-migrationsSean McGivern2016-06-091-0/+1
| | | | | | | Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file.
* Add release modelDmitriy Zaporozhets2015-11-051-0/+14
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
View Lorry Controller Status