Level 1
I forced the commit of the 1 file and it pushed to GitHub. still not sure why it didn't go by default with the rest of the project.
Apr 22, 2020
2
Level 1
migration files not moving to GitHub, Forge deployment then fails.
another noob question...
I'm using Laravel Framework 6.18.0 on Windows 10, PhpStorm, GitHub, Forge and AWS
I needed to change my model and add a column to a table. Worked find on my local machine.
When I did the commit/Push (in PhpStorm) to Github the php/html code moved but the migration file didn't and then I had a an issue with the hosted site (test for now so not a big issue as I'm learning the nuances of the platform). the upside is that its made me put in a lot more error checking :-)
What is the secret to getting the migration files to move to GitHub and why didn't they move with the commit/Push? is this a feature? or did I misconfigure something?
Level 1
I think i get it now. its because you can change the migration 10 times before you want it to go into production. check...
Please or to participate in this conversation.