Deploying YAML Schedules from a Custom Branch

• The modular .bolt/ folder
• The legacy flat paradime_schedules.yml file

​

When to use this

• You keep a long-lived release branch and want schedules to track it instead of main.
• You maintain a dedicated bolt-config branch for schedule changes, separate from your dbt model PRs.
• You’re staging a large schedule refactor on a branch and want to deploy from it before merging.

​

How it works

• Parse-schedules reads schedule YAML from the configured branch.
• The Bolt YAML editor in the Paradime UI reads from, and commits to, the configured branch.
• The repository’s default branch is ignored for schedule purposes (it is still used everywhere else — git_branch defaults, PR targets, etc.).

​

Setting the branch

mutation SetScheduleDeploymentBranch($branch: String) {
  setScheduleDeploymentBranch(branch: $branch) {
    ok
  }
}

• Pass a branch name (e.g. "release-2026-05") to set the override.
• Pass null (or omit the argument) to clear the override and revert to the default branch.

​

Deployment behaviour

• Automatic Refresh: Paradime checks for changes every 10 minutes.
• Manual Refresh: Open Bolt and click Parse Schedules to refresh immediately.