From 7445dd72607e4e6900ac34a45767167ef75fb359 Mon Sep 17 00:00:00 2001
From: JuanDMeGon <JuanDMeGon@users.noreply.github.com>
Date: Mon, 27 Sep 2021 18:32:30 -0500
Subject: [PATCH] Keeping access tokens migration id consistent

This is just a tiny "fix," using id(); to be consistent with the other migrations already included in the framework.
---
 .../2019_12_14_000001_create_personal_access_tokens_table.php   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database/migrations/2019_12_14_000001_create_personal_access_tokens_table.php b/database/migrations/2019_12_14_000001_create_personal_access_tokens_table.php
index 3ce00023a9e..4315e16a85a 100644
--- a/database/migrations/2019_12_14_000001_create_personal_access_tokens_table.php
+++ b/database/migrations/2019_12_14_000001_create_personal_access_tokens_table.php
@@ -14,7 +14,7 @@ class CreatePersonalAccessTokensTable extends Migration
     public function up()
     {
         Schema::create('personal_access_tokens', function (Blueprint $table) {
-            $table->bigIncrements('id');
+            $table->id();
             $table->morphs('tokenable');
             $table->string('name');
             $table->string('token', 64)->unique();