Sync

Sync deploys a pull request's state to an environment on demand, from a comment on the PR — without waiting for a merge, build, and release.

Where the other branch operations move a change between branches, Sync moves the state of a branch onto an environment. It deploys a pull request's current state to an environment on demand — straight from a comment on the PR — without waiting for a merge, a build, and a release.

codev posts the sync commands on every pull request.

There are two forms, for two situations:

Command	What it does	Approval
Sync review environment	Brings this PR's own review environment up to the full PR branch state.	Not required — the blast radius is your own PR.
Sync to a named environment	Deploys this PR's changes to a named, shared environment (e.g. qa, staging).	Required — a shared environment is the exception, not the default.

Reach for the review environment first; treat syncing to a shared environment as the exception, since it puts unmerged code where other people test and can make the environment drift from what the release process says is deployed there.

Full setup, the exact commands, approval behaviour, and guidance on when to use each form are in Syncing Environments.

Related

• Syncing Environments — the full reference for both sync forms
• Environments — how an environment tracks a branch
• Tracking additional branches — which branches codev builds and deploys