> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploying YAML Schedules from a Custom Branch

By default, Paradime reads schedule YAML from your repository's **default branch** (usually `main` or `master`). If you want schedules deployed from a different branch, an admin can set a workspace-level **schedule deployment branch** override.

This applies to both layouts:

* 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

While a custom schedule deployment branch is configured:

* **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.).

Clearing the setting reverts to the default branch.

<Warning>
  The custom branch must already exist in the connected Git repository. Paradime does not create it for you.
</Warning>

***

#### Setting the branch

The schedule deployment branch is a workspace-level setting. Admins can configure it through the Paradime UI under workspace settings, or programmatically via the GraphQL API:

```graphql theme={"system"}
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

The refresh cadence is the same regardless of which branch is used:

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

<Info>
  💡 **Note**: To update your schedules, merge (or push) your changes to the configured branch first. Commits to other branches are ignored.
</Info>


## Related topics

- [Modular Schedules with the .bolt/ Folder](/products/bolt/creating-schedules/schedules-as-code/modular-schedules-with-the-.bolt-folder.md)
- [Editing YAML Schedules from the Paradime UI](/products/bolt/creating-schedules/schedules-as-code/editing-yaml-schedules-from-the-paradime-ui.md)
- [Schedules as Code](/products/bolt/creating-schedules/schedules-as-code/index.md)
- [Schedule Configurations](/products/bolt/managing-schedules/schedule-configurations.md)
- [Bolt API](/developers/graphql-api/api-reference/bolt-api.md)