Deployment source

Open the app, then Configuration → Deployment Source. Choosing the repository needs kernel/deployments/read in the boundary as well, which the Apps Operator role includes.

Change the repository or branch

1. Choose the Deployment Source Type — GitHub, GitLab or Azure DevOps.
2. Pick the installation, the Repository and the Branch. Picking a repository selects its default branch. A source that is not connected yet can be added from here — see Add a source.
3. Choose Save.

A new branch is built from its latest commit and deployed. A version you pinned with Redeploy this version is let go, and pushes to the new branch deploy the app from then on — see Automatic deployments.

Changing the branch here changes the app itself. A slot builds its own branch — see Deployment slots.

Change the container image

Choose Container Registry and enter the full image reference in Container Image, registry/name:tag or registry/name@sha256:…. The cluster pulls it without credentials from you — see Where the code comes from. Save, and new instances start with the new image.

Moving an app from a repository to a container image, or back, is done the same way. The runtime stack and version are not used while the app runs a container image.

Git (Direct URL)

The list also offers Git (Direct URL), a repository address and branch without a deployment source. The platform can clone only through a deployment source, so an app set to a direct URL cannot be built. Connect the repository's provider as a deployment source and choose it instead.