Luke Towers

Closing as it has been over a month since any activity on this occurred and we are trying to figure out what issues are still relevant. If this is still...

Tests are failing because of a byproduct of the ochestra testbench setup, the scaffolded files are being generated inside of vendor/orchestra/testbench-core/laravel/$absolutePathToOrchestraTestBenchCoreLaravel; investigating further

The failing test is passing locally, not sure why and can't rerun it on here.

@taylorotwell I'm not sure how the infinite loop could be solved without also asking the user for more information on what namespace the class should be generated in. And if...

@lex0r can you provide a usage example for this?

@damsfx what sort of impact will this have on your workflow? I was thinking that if anyone misses it when reviewing the next version they'll catch it on the first...

@IsaiahPaget could you submit a PR for the docs as well please?

@bennothommo this has been the default behaviour in Laravel [since 2014](https://github.com/laravel/framework/commit/45fbe5448f03ce9c0344bcdee9bcdc6d226ff943). @IsaiahPaget to minimize disruption to existing installs, let's target wip/1.3 and let's use the config key `database.migrations.confirm_in_prod`. We'll add...

@bennothommo fair enough. The primary reason I wanted to add support was so that the CLI was more consistent between Winter and Laravel. I could be convinced to make the...

@IsaiahPaget See my latest comment on the PR. Laravel 12 [made the `database.migrations` config item an array](https://github.com/laravel/framework/blob/12.x/config/database.php#L129-L132) so it's easier for us to add our own keys in there rather...