From 35057ceceebe4684f06eb74414c74481f2085008 Mon Sep 17 00:00:00 2001 From: Ihor Rud Date: Wed, 10 Dec 2025 11:00:03 +0200 Subject: [PATCH 1/2] docs: use proper naming convention for model Flight --- migrations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/migrations.md b/migrations.md index 99e24eec60..aa468e0213 100644 --- a/migrations.md +++ b/migrations.md @@ -140,7 +140,7 @@ public function up(): void Sometimes a migration might be meant to support a feature that is not yet active and you do not want it to run yet. In this case you may define a `shouldRun` method on the migration. If the `shouldRun` method returns `false`, the migration will be skipped: ```php -use App\Models\Flights; +use App\Models\Flight; use Laravel\Pennant\Feature; /** @@ -148,7 +148,7 @@ use Laravel\Pennant\Feature; */ public function shouldRun(): bool { - return Feature::active(Flights::class); + return Feature::active(Flight::class); } ``` From 0bfabedf37b55c4ed88896a0002e5e1ebac10ac5 Mon Sep 17 00:00:00 2001 From: Ihor Rud Date: Wed, 10 Dec 2025 11:03:29 +0200 Subject: [PATCH 2/2] docs: add link to Isolating Migration Execution section --- migrations.md | 1 + 1 file changed, 1 insertion(+) diff --git a/migrations.md b/migrations.md index aa468e0213..0e509c365e 100644 --- a/migrations.md +++ b/migrations.md @@ -173,6 +173,7 @@ If you would like to see the SQL statements that will be executed by the migrati php artisan migrate --pretend ``` + #### Isolating Migration Execution If you are deploying your application across multiple servers and running migrations as part of your deployment process, you likely do not want two servers attempting to migrate the database at the same time. To avoid this, you may use the `isolated` option when invoking the `migrate` command.