In your case, we can proceed in two ways:
1. To write a new migration where you change the structure of the table and do php artisan migrate
2. "To perinatality" all migrations again by killing the current structure (Attention, data loss)
And most importantly -- it is good to read what is migration and why they are used.
jaquan answered on March 19th 20 at 09:24
No way. Migration to change after production NOT only to write a new one. Actually, this makes sense.
Again, if the prod - make migrate:fresh --seed
If the prod - create a NEW migration, type alter_users_table_add_avatar inside of Schema::table() and forward.