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 |
|
Bob Van Landuyt
|
4b9eab02b8
|
Reject EE reserved namespace paths in CE as well
|
2017-05-04 18:11:31 +02:00 |
|
Bob Van Landuyt
|
2e2a63c866
|
Rename child namespaces in migrationhelpers
|
2017-05-01 11:14:24 +02:00 |
|
Bob Van Landuyt
|
99a03fd6e9
|
Move ReservedPathsMigration into V1 namespace
|
2017-05-01 11:14:24 +02:00 |
|
Bob Van Landuyt
|
389057f001
|
Rename Projects & Namespaces based on entire paths
|
2017-05-01 11:14:24 +02:00 |
|
Bob Van Landuyt
|
ab5f9027fb
|
Rename namespaces called `Users`
This should rename the already created namespace that snuck trough
because the validation was case sensitive
|
2017-05-01 11:14:24 +02:00 |
|
Bob Van Landuyt
|
e3d6957812
|
Rename forbidden paths in a single migration
|
2017-05-01 11:14:24 +02:00 |