Skip to main content
The riskier the environment, the more review it should need. Revolte lets you set this per environment, so a Preview can move quickly while Production waits for a person.
1

Map branches to environments

Decide which Git branches deploy to Production, Staging and QA. See Configure app and branch settings.
2

Add quality gates before the build

Run code review, code quality and tests before every build. Set them per environment where you need different rules. See Configure pre-build workflows and Environment pre-build flow.
3

Require approval for sensitive environments

Add a manual approval gate to the pipeline so a person approves before a deployment continues. See Pipelines and approvals.
4

Commit the configuration

Changes made in the Revolte UI take effect only after you commit them back to your repository. See Sync configuration changes.

Example policy

This is an example, not a default. Adjust it to your own risk.

Where people decide

See Approval gates and audit logs for how gates and records work, and the human-in-the-loop model for the three checkpoints that apply to every task.

Next

Roll out Revolte across teams

Admin and security