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
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
260a915cb0
Fix group visibility level migration in case all visibility levels are restricted
2016-05-19 20:08:08 -04:00
503244eb96
Fix specs
2016-03-22 00:23:58 +01:00
31266c5be4
Address feedback
2016-03-22 00:09:20 +01:00
8d544645f0
Add specs and add visibility level to admin groups
2016-03-21 19:11:24 -03:00
8db1292139
Tweaks, refactoring, and specs
2016-03-20 21:04:07 +01:00
0a7f716119
Code fixes
2016-03-17 19:42:46 -03:00
ec20fdf366
Code improvements and add Create group service
2016-03-16 19:44:33 -03:00
c3e70280df
Prevent projects to have higher visibility than groups
...
Prevent Groups to have smaller visibility than projects
Add default_group_visibility_level to configuration
Code improvements
2016-03-10 10:38:36 -03:00
Jan Provaznik