Laravel PreShift

[nomadjimbob]

This pull request contains changes from the Laravel PreShift to give you a feel for running Shift. All Shifts open a pull request with the changes in nice, atomic commits. This allows you to review each change in isolation.

Shift also leaves detailed comments for any additional manual changes you may need to make, or changes you may want to implement to follow the latest conventions.

To complete a Shift:

• Checkout the shift-165916 branch
• Review all pull request comments
• Thoroughly test your application

If you have any issue with your Shift, never hesitate to contact support@laravelshift.com, or check out the Human Shifts for more hands-on support.

[nomadjimbob]

ℹ️ Shift detected you are currently on Laravel 12.0. This is the latest version of Laravel. As such, you do not need to upgrade Laravel.

You may consider running the Laravel Fixer to ensure your application follows the latest Laravel conventions, or some of the automation available within the Shift CLI.

[nomadjimbob]

⚠️ Shift did not detect a code style within your project. All Shifts format your code to "normalize" files before performing comparisons. This improves the automation.Shift supports Pint, PHP CS Fixer, or PHP CodeSniffer. By default, Shift will apply the Laravel code style as defined by Pint. For more information on customizing the code style applied by Shift, you may watch this short video.

[nomadjimbob]

ℹ️ All Shifts bump core Laravel dependencies as well as popular community packages. However, some packages may have their own upgrade steps. To make review easier, Shift will note packages which are bumped major versions, as well as packages which were not bumped or potentially abandoned. For now, Shift did not detect any packages which are not tracked or marked as abandoned.

[nomadjimbob]

ℹ️ Shift did not detect any tests other than the default Laravel tests provided by Laravel. Having tests not only gives you confidence that your application is behaving as expected, but also makes it easier to verify upgrades.

You can get started with writing tests by running the Tests Generator to quickly stub PHPUnit (or Pest) tests for all the controller actions and commands in your application.