Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi all,
i've a question for the best way to use the quick deploy with laravel forge.
In my development environment the process for an issue is this: Open -> In Work -> Review -> Test -> Verified -> Merged(Finished)
In practice there are many issues in testing and the employee, who tests the issues, works only some days per week and verify the issues. So i come back in office in the morning and have for example 5 issues verified. Now i merge this 5 issues back in the development branch and the forge quick deploy starts 5 deploys in a short time.
Is there a better way to handle this, that i have only one deploy when merging lots of issues?
Regards Bastian
Hi Bastian,
The problem seems to be the fact that it's either your IDE or some git hook you have installed that is pushing your code after each merge. Resolve that, and the problem will be gone. Only when I git push my changes to, say, GitLab, Forge will auto deploy it for me to the server.
HTH, Michal
Hi Michal,
thank you for your feedback.
But i have no idea how to reslove this because i'm using Jira and Bitbucket. If a Issue in Jira is finished i can directly merge the open pull request in bitbucket and then the code doesn't need a push. The only thing i could to is, to work manually on all pull requests on my local machine. This is not the best way i think.
Bastian
Please or to participate in this conversation.