6 Commits

Author	SHA1	Message	Date
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
Rémy Coutable	a59e75a17f	Make the downtime_check task happy ... Signed-off-by: Rémy Coutable <remy@rymai.me>	2016-11-30 16:15:02 +01:00
Rémy Coutable	c33b489853	Add `null: true` to timestamps in migrations that does not define it ... 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>	2016-11-28 16:45:08 +01: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
Ciro Santilli	9b5c7a4d60	Add star count, view logic, more tests.	2014-07-17 22:47:16 +02:00
Ciro Santilli	714f7201d3	Add project stars.	2014-07-17 22:47:16 +02:00