Skip to main content

​
How to configure

Follow these steps to define your application identity and branch strategy.
1

Access Repo Preferences

Navigate to YAML Configuration > Repo Preferences from your project dashboard.
2

Map Branches

Assign specific Git branches to your Production, UAT, and QA environments.
3

Commit Changes

Enter a commit message and select your target branch to persist the changes. See Syncing Changes for a detailed walkthrough.

​
Branch mapping

Map your Git branches to Revolte environments to enable automated deployments.
Git BranchRevolte EnvironmentBehavior
mainProductionLive production traffic and primary rollout target.
stagingUATPre-production validation and user acceptance testing.
qaQAAutomated testing and quality assurance cycles.
* (Any other)PreviewEphemeral environments with a default 3-day retention period Customizable .
revolte.yaml
revolte:
  version: "1.0"
  project: Demo-Project
  appName: "demo-app"
  env:
    production:
      branch: main # Maps production environment to the main branch
    staging:
      branch: staging # Maps UAT environment to the staging branch
    qa:
      branch: qa # Maps QA environment to the qa branch
How to Customize Preview Expiry:By default, Preview environments automatically destroy themselves after 3 days. To adjust this lifespan:
  1. Open your project dashboard and select Settings from the left navigation bar.
  2. Navigate to General Settings > Preview environment expiry.
  3. Enter your preferred duration, select the unit (Day or Hour), and click Update.
Note: This applies to upcoming deployments only.

​
Service integration

Branch mapping triggers automated deployments for all services in the environment.
revolte.yaml
revolte:
  env:
    production:
      branch: main
      services:
        rid_1:
          type: WEB_SERVICE
          name: api-gateway
          # Revolte deploys this service when code is pushed to 'main'