Does Shift upgrade everything?

Not everything.

Shift attempts to upgrade your Laravel project so you just need to run composer install. However, given the dynamic nature of PHP and the infinite customization of a Laravel project, this is not always possible. When Shift can not reliably perform an upgrade, a detailed comment will be added to the Pull Request for you to review.

Does Shift upgrade more than the Laravel Upgrade Guide?

Yes.

The Upgrade Guide focuses on new features and breaking changes, treating the rest optional. Over time, upgrades following this approach accumulate technical debt.

Shift attempts to upgrade all changes. This ensures your project is fully up-to-date with your version of Laravel.

What if my project is not on Bitbucket/GitHub?

Currently we only support Bitbucket and GitHub. Using these services allows Shift to easily access your Laravel projects and submit the upgrade for your review.

Both services offer free public repositories. And if privacy is a concern, Bitbucket offers free private repositories. So there's nothing stopping you from adding your project to Bitbucket or GitHub so you can use Shift.

Why do you need full access to my repositories? Having full access to your repositories allows Shift to be added as a collaborator automatically. This way the process can be seamless from start to finish.

Once you merge the Pull Request, you are welcome to deauthorize the Laravel Shift application and remove laravel-shift's access from your repository.

Does Shift keep a copy of my code?

No.

Your Laravel project only lives on the Shift build server during the upgrade process. On average, this lasts 19 seconds. Afterward your Laravel project is forcefully removed.