Deployment branch

By default, only pushes to the master branch get deployed. But you can change this by calling a REST API on the Kudu service. One simple way to do this is to use curl.

Here is an example:

# Switch branch (/settings endpoint)
$ curl https://user:pass@site.scm.azurewebsites.net/settings \
       --data "{key: 'branch', value: 'anotherbranch' }" \
       -H "Content-Type: application/json; charset=UTF-8"


$ cat body.json
{
    "format": "basic",
    "url": "https://github.com/username/projectname"
}


# Trigger a deployment (branch name is read from /settings)
$ curl -X POST https://user:pass@site.scm.azurewebsites.net/deploy \
       --data @body.json \
       -H "Content-type: application/json"

Which results in:

The Azure portal (portal.azure.com) also has UI to change this:
Deployment options blade -> Disconnect -> Setup -> Choose branch. This currently doesn't work in the 'local git' case.

As an alternative, you can set the branch by setting an Azure App Setting called deployment_branch.