Feature Request: Allow Deployment of Git Branch Other Than Main to a Development Environment #907
Replies: 3 comments
-
To change the deployment branch, you can do some Kudu magic, by sending a POST request to https://[your-project].scm.euwest01.umbraco.io/settings with the following JSON body {
"key": "deployment_branch",
"value": "[the branch you want to deploy from]"
} The request needs basic authentication with your cloud user and password. |
Beta Was this translation helpful? Give feedback.
-
@skttl could this be added to the ci/cd setup? |
Beta Was this translation helpful? Give feedback.
-
Thanks for the tip @skttl ! I'd still like to keep this feature request open since my thought is that it would be ideal to be able to do this from the portal when adding a new flexible environment to a project. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue description
Umbraco Cloud deployments use the "master" (or "main") branch when deploying to a Development environment. I propose allowing deployments from other Git branches. Additionally, I suggest providing an option to create a new environment directly from a specific Git branch (using the Flexible Environment feature). This flexibility will enable teams to test features, bug fixes, and other changes in isolated environments before merging them into the main branch.
I expect there are some additional considerations to be taken with this feature. Please feel free to add comments.
Beta Was this translation helpful? Give feedback.
All reactions