Source overrides

By default, all environments in a project inherit the project-level source — the repository and branch set when the project was created. A source override lets one environment use a different branch, commit, or archive without affecting other environments.

A common use: keeping main on your production environment while a staging environment tracks a develop or release branch.

Setting a source override

Open the environment, go to the Source tab, and switch from Inherit project source to a custom source.

For GitHub projects, you can override the branch and commit. The repository and root directory are locked to the project's settings — you cannot point an environment at a different repo or subdirectory.

For archive projects (upload), you can upload a new archive specific to this environment.

Click Save to apply the override. Saving does not automatically trigger a new deployment — go to the Deployments tab and deploy manually.

Only organization Owners and Admins can change the source of an environment.

Source changes are blocked while a deployment or other operation is in progress.

Removing a source override

On the Source tab, switch back to Inherit project source and save. The environment will use the project's default source on the next deployment.

Commits: specific vs latest

When setting a GitHub source, you can choose:

A specific commit — the environment always deploys that exact commit until you change it.
Latest commit on branch — the environment deploys the latest commit on the selected branch each time a deployment is triggered.