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
Tiago Botelho
c41df67676
removes redundant code from database.rb
2017-04-11 20:20:19 +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
Stan Hu
13c00262f7
Use false/true mixin in migration from !3640
2016-04-10 22:04:24 -07:00
Stan Hu
3b77a07856
Fix more SQL migrations to use raw commands
...
gitlab-org/gitlab-development-kit#109
2016-04-10 15:51:45 -07:00
Valery Sizov
47f539f5a6
Snippets: public/internal/private
2014-10-09 17:09:53 +03:00
