Robin Ward ce78eff888 FIX: Migration paths were being forgotten ... According to the [Rails Source](https://github.com/rails/rails/blob/master/activerecord/lib/active_record/railties/databases.rake#L20) the `ActiveRecord::Migrator.migrations_paths` are overwritten with the value of `ActiveRecord::Tasks::DatabaseTasks.migrations_paths` every time the config is loaded. This caused a bug for Discourse development where if you ran: `rake db:drop db:create db:migrate` in one line, you would not get our post migrations, as those had a custom value for `migrations_paths`. The fix is to use `ActiveRecord::Tasks::DatabaseTasks.migrations_paths` to set up all our custom paths. Everything seems to work as expected.		2019-12-16 14:13:47 -05:00
..
json_rows_formatter.rb
reporter.rb
runner.rb	FIX: Migration paths were being forgotten	2019-12-16 14:13:47 -05:00