Development environments
Configure the branch, setup script, run command, and secrets a repo uses.
Each repository connected to Proliferate has its own Repo settings, reachable by switching to that repository from the repo picker in Settings. It controls what happens when an agent creates a workspace for that repo, and it has three tabs.
Cloud-side settings here are shared: everyone on the team who works on that repo through Proliferate cloud gets the same setup script, run command, and environment variables. Local-side settings are personal to your own machine and aren't shared with teammates.
Configure
Sets the default branch new workspaces branch from.
Repo > Configure
Repo settings, Configure tab: a branch picker for the repo's default branch, separate for the Cloud and Local context.
Actions
Sets the scripts that run around an agent's workspace:
- Setup script. Runs once when the workspace is created (a cloud sandbox
is provisioned, or a new local worktree is created). Use it for install
steps like
pnpm installorpnpm prisma generate. Local setup scripts getPROLIFERATE_WORKTREE_DIR,PROLIFERATE_REPO_DIR,PROLIFERATE_BRANCH, andPROLIFERATE_BASE_REFas environment variables. - Run command. A single command launched by the workspace's Run action,
for example
make dev.
Repo > Actions
Repo settings, Actions tab: a setup script editor and a run command field, separate for the Cloud and Local context, with detected setup-command suggestions for local repos.
Environment
Variables and files synced into cloud workspaces created for this repo.
Repo > Environment
Repo settings, Environment tab: the list of environment variables and files synced into cloud workspaces for this repo, with add, replace, and delete controls.
This store is cloud-only. Local workspaces read environment variables from your shell and whatever's already in your checkout; there's no separate local environment store to configure.
Who can change this
Anyone with access to the repo through Proliferate can open its Repo settings. Because cloud-side Configure, Actions, and Environment settings are shared across the team, treat them the way you'd treat a checked-in CI config: changes affect every teammate's next cloud workspace for that repo.
Related
- Data boundaries for how repo environment variables relate to personal and organization secrets.
- Organizations