Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi I have both a production site and testing site maintained via Forge. Until today both production and testing were set up to use my Master branch which was based on Laravel 5.7. I want to move to Laravel 5.8 so I created a branch (called Upgrade-to-5.8) and with my IDE worked through the various issues.
I now have both Master and Upgrade-to-5.8 branches available on Github.
In Forge I accessed my test server site and changed the Deployment Branch from Master to Upgrade-to-5.8 and ran Deploy Now. Below is a portion of the deployment log where it appears that the master branch was deployed rather than my Upgrade-to-5.8 branch.
Is there something else that I need to do to change my branch on this site?
Wed Aug 28 21:12:57 UTC 2019
From github.com:XXXXXX(Changed for security purposes)
* branch master -> FETCH_HEAD
Already up to date.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating optimized autoload files
@dalma In your "deployment script" you also need to update the following line
git pull origin master
And change it your branch name
git pull origin Upgrade-to-5.8
The reason this doesn't work is because the branch name you give it is the trigger branch name, but the deployment script can still be different from that.
Let me know if that works for you ;)
@dalma I had the same issue. @bobbybouwmann 's post is the solution.
Please or to participate in this conversation.