It is generally good practice to have database changes in source control. You can achieve this by using laravels migrations. It is much harder to keep track of manual changes even if you document them. I assume your are not documenting the changes because it probably wouldn't be quicker.
It probably wont hurt you right now but what if you run multiple databases for multiple environments. Each contributing dev has to make the same changes to their own local environment. The time spend changing them manually quickly grows where as a migration can easily be automated.
It also greatly increases your ability to redeploy your project.
This answer has a must read link about why it is good to have database migrations in source control
https://stackoverflow.com/a/115382/6242681