Not everything.
Shift attempts to upgrade your Laravel application so you just need to run composer update. However, given the dynamic nature of PHP and the infinite customization of a Laravel application, this is not always possible. When Shift can not reliably perform a change, a detailed comment will be added to the Pull Request for you to review.
Yes.
The Upgrade Guide focuses on new features and breaking changes, treating the rest as optional. Over time, only following the Laravel Upgrade Guide accumulates technical debt.
Shift upgrades all changes. This ensures your project is fully up-to-date with your version of Laravel and there are no future surprises. It'll be like your project was running that version of Laravel all along.
No. This is by design to improve context and focus. Doing so incrementally allows you to verify each upgrade to ensure you don't miss anything.
For tips on completing Shifts efficiently and keeping your app upgradable, watch the Shift like a Pro and Maintaining Shiftability videos.
Currently, these are the services which allow you to quickly connect your Laravel application to Shift.
All of these services offer free private repositories. So you can always push a temporary copy of your repository to run Shift.
Having write access to your repositories allows Shift to create a new branch and open a Pull Request. This way the process can be seamlessly automated from start to finish.
Once you merge the Pull Request, you are welcome to deauthorize the Laravel Shift application.
No.
Your code only lives on the Shift server while the upgrade process is running - less than a minute on average. After it completes, your code is forcefully removed from the Shift server. We're talking rm -rf *.
I realize some code comes with policies or agreements which prevent you from sharing it in any way.
That's why I built Shift for Docker - so you can run any Shift against one of your Laravel applications entirely locally.
Yes.
Simply start your order process. Once you reach checkout, send payment via PayPal to payments@laravelshift.com and include your Shift number.
All Shifts are single use. This is by design. For example, you don't need to upgrade the same version twice.
Of course if there is an issue, or you believe the automation might be improved by making some changes, you may request a rerun by sending your Shift number to support.
If a Shift fails, you will receive guidance on how to resolve the problem. Once you have, you may rerun your Shift. If the rerun fails, you may contact support to take a look.
For basic support feel free to message @laravelshift on Twitter or email support@laravelshift.com.
If you want hands-on support with upgrading your application, Laravel, or PHP, check out the Human Shifts.
Still have questions? Message @laravelshift on Twitter or email support@laravelshift.com.
Sign in with any of the following services to connect Shift with your Laravel project.
Don't use one of these services?
Temporarily push your project to a free, private repository on one of these cloud-based services or upgrade your project locally with Shift for Docker.