levizoesch / laravel-check-migrations

A Laravel command scans your application for pending migrations, providing a clear overview of what needs to be migrated. You can then choose to run individual migrations or skip them as needed, short-cutting and optimizing your development workflow.

Check Migrations

A Laravel command scans your application for pending migrations, providing a clear overview of what needs to be migrated. You can then choose to run individual migrations or skip them as needed, short-cutting and optimizing your development workflow.

Support for Structured Migrations

This package seamlessly handles migrations organized within subdirectories, ensuring that no pending migrations are overlooked regardless of the project's migration structure.

database
└── migrations
├── 2023_01_01
│ ├── 20230101000001_create_table_one.php
│ └── 20230101000002_create_table_two.php
└── 2023_02_01
├── 20230201000001_create_table_three.php
└── 20230201000002_create_table_four.php

Installation

composer require levizoesch/laravel-check-migrations

Usage

Run the following command in your terminal:

This will display pending migrations and prompt for confirmation before running each one.

php artisan check-migrations

This will skip confirmation and run pending migrations directly.

php artisan check-migrations --skip

This will ignore the migration named 20230101000000_create_example_table from running and prompting for confirmation.

php artisan check-migrations --ignore=20230101000000_create_example_table

Notes

Ensure that your Laravel project is properly configured and migrations are set up correctly for this command to work effectively.

Always review pending migrations before running them in production environments to prevent unintended consequences.

Known Issues

Double Confirmation Prompts in Production

When running the check-migrations command in a production environment, users may encounter double confirmation prompts. This occurs due to Laravel's native migrate command prompting for confirmation before migrating when in production mode. Since the check-migrations command internally calls the migrate command for each pending migration, users may be prompted twice for confirmation for each migration.