Jan Provaznik
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
Douglas Barbosa Alexandre
fed29117de
Rename SlackNotificationService back to SlackService
2016-12-20 19:42:13 -02:00
Felipe Artur
a5ccaded65
Change SlackService to SlackNotificationsService
2016-12-15 15:32:49 -02:00
Sean McGivern
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
Douwe Maan
4803af45df
Prevent another migration from failing.
2015-02-25 22:55:37 +01:00
Dmitriy Zaporozhets
ff48e1eeb7
Save only valid record in service migrations
...
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2014-10-31 11:12:41 +02:00
Marin Jankovski
eceef546d1
Add slack service migration.
2014-10-06 16:50:24 +02:00