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 |
|
Shinya Maeda
|
1024718e9f
|
Refactor access_level to not_protected and ref_protected
|
2017-09-03 23:49:10 +09:00 |
|
Shinya Maeda
|
eda34b1a18
|
Add spec. Fix runner setting page. It worked.
|
2017-09-03 23:49:10 +09:00 |
|
Shinya Maeda
|
e1ef436d1f
|
Update application code by the db schema change
|
2017-09-03 23:49:10 +09:00 |
|
Shinya Maeda
|
0a7b3ae9f1
|
Re-organize schema. Drop protected from runner. Add access_level to runner. Drop protected from pipeline. Add protected to ci_bilds.
|
2017-09-03 23:49:10 +09:00 |