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 |
Douwe Maan
|
29a32cfc22
|
Migration does not require downtime
|
2017-02-08 19:20:27 -06:00 |
Douwe Maan
|
63c5b541a3
|
Satisfy the new rubocop :)
|
2017-02-08 18:12:16 -06:00 |
Rémy Coutable
|
2cf7f09b1e
|
Revert "Revert "Merge branch '18193-developers-can-merge' into 'master'
""
This reverts commit 530f5158e2 .
See !4892.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
2016-07-18 10:16:56 +02:00 |
Robert Speicher
|
530f5158e2
|
Revert "Merge branch '18193-developers-can-merge' into 'master'
"
This reverts commit 9ca633eb4c , reversing
changes made to fb229bbf79 .
|
2016-07-13 13:57:30 -05:00 |
Mathias Vestergaard
|
f0577d8385
|
Added "developers can merge" setting to protected branches
- Cherry-picked from `mvestergaard:branch-protection-dev-merge`
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4220
|
2016-07-13 13:24:26 +05:30 |