resolve conflict in the migrations folder,by forcing to publish the migration before migrating it.

Author: darbaoui

README.md

@@ -19,16 +19,16 @@ composer require devinweb/laravel-hyperpay
 
 ## Database migration
 
-`Laravel-hyperpay` provides a migration to handle its own transaction, don't forget to run the migration after installation
+`Laravel-hyperpay` provides a migration to handle its own transaction, don't forget to publish the migration after installation
 
 ```bash
-php artisan migrate
+php artisan vendor:publish --tag="hyperpay-migrations"
 ```
 
-If you want to make an update or change the path of the migration, you can publish it using `vendor:publish`
+Then migrate
 
 ```bash
-php artisan vendor:publish --tag="hyperpay-migrations"
+php artisan migrate
 ```
 
 This migration has a model named `Transaction`, if your app use [multi-tenancy](https://tenancy.dev/docs/hyn/5.5/installation), you can create a new transaction model based on the `hyperpay transaction` model.

src/LaravelHyperpayServiceProvider.php

@@ -17,7 +17,6 @@ public function boot()
         $this->registerRoutes();
         $this->registerResources();
         $this->registerPublishing();
-        $this->registerMigrations();
     }
 
     /**
@@ -70,17 +69,6 @@ protected function registerPublishing()
         }
     }
 
-    /**
-     * Register the package migrations.
-     *
-     * @return void
-     */
-    protected function registerMigrations()
-    {
-        if ($this->app->runningInConsole()) {
-            $this->loadMigrationsFrom(__DIR__.'/../database/migrations');
-        }
-    }
 
     /**
      * Register the application services.