From ea2cbbb034dd55f82ce4db331ffb754b0fc718fa Mon Sep 17 00:00:00 2001 From: Roardom Date: Wed, 9 Apr 2025 21:30:03 +0000 Subject: [PATCH] fix: don't import schema file when in schema dump ci If you're importing the same file as you're editing, it's not too useful. For example, one could edit the schema, add an entry to the bottom to the migrations table, and the ci will import it when running all migrations before generating the new dump. The new dump would therefore include what the schema file already had instead of the sql that the laravel migrations generated. --- .github/workflows/schema-dump.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/schema-dump.yml b/.github/workflows/schema-dump.yml index 1d3a015c5..8629ab0a4 100644 --- a/.github/workflows/schema-dump.yml +++ b/.github/workflows/schema-dump.yml @@ -54,7 +54,7 @@ jobs: - name: Clear Application Cache run: php artisan optimize:clear - name: Run Migrations - run: php artisan migrate --force + run: php artisan migrate --force --schema-path=database/schema/mysql-schema-new.sql env: DB_CONNECTION: mysql DB_HOST: 127.0.0.1