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
Lin Jen-Shin
b95da565cd
Enable rubocop for db/**/* and ee/db/**/*
2018-07-25 17:47:12 +08: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
Robert Speicher
a9103eae3a
Make more migrations reversible
...
[ci skip]
2015-05-13 11:03:29 -04:00
Vinnie Okada
bd557e4b64
Add new admin settings
...
Add new global application settings for default project and snippet
visibility levels.
2015-04-26 07:48:19 -06:00