Does Shift automate everything?
Shift attempts to automate everything. However, given the dynamic nature of PHP and the infinite ways to write code, this is not always possible. When Shift can not reliably perform a change, a detailed comment will be added to the Pull Request so you can review.
Should I merge each Shift before doing another?
You should review and merge each Shift before running the next. Doing so incrementally allows you to test each Shift in isolation to ensure you don't miss something.
What if my project is not on Bitbucket/GitHub/GitLab?
These services offer free public repositories. If privacy is a concern, Bitbucket and GitLab offer free private repositories. So there's nothing stopping you using Shift.
Why does Shift 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 PHP Shift application and remove php-shift's access from your repository.
Does Shift keep a copy of my code?
Your PHP code only lives on the Shift server during the upgrade process. On average, this lasts under a minute. Afterward your PHP code is pushed to your repository and forcefully removed from the Shift server.
What happens if things go wrong?
During checkout, Shift will verify access to your repository and charge your credit card. If anything goes wrong you will receive an error message so you may resolve the issue.
Once checkout is complete, your Shift is added to the job queue. If a Shift fails, you will receive an email notification with some things to check on your side before trying to run your Shift again.
Does Shift offer additional support?