0fc9f9d3e7
Add version 4.2 to all existing migrations
...
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
2018-11-22 13:18:28 +01:00
b95da565cd
Enable rubocop for db/**/* and ee/db/**/*
2018-07-25 17:47:12 +08:00
c41df67676
removes redundant code from database.rb
2017-04-11 20:20:19 +01:00
98bb435f42
Enable RuboCop for migrations
...
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.
2016-06-09 16:05:25 +01:00
208f99ff6c
Fix MySQL migration of CI emails [ci skip]
2015-12-14 12:04:26 +01:00
a0c2a7b0cb
Fix migrations [ci skip]
2015-12-14 11:30:32 +01:00
e365750199
Enhance migrate CI emails
2015-12-11 13:25:50 +01:00
80f8074d01
Migrate SlackService and HipChat service
2015-12-10 16:04:08 +01:00
d5c91bb9a6
Migrate CI WebHooks and Emails to new tables
2015-12-10 16:04:08 +01:00
Jan Provaznik