> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/bolt/creating-schedules/schedules-as-code/deploying-yaml-schedules-from-a-custom-branch.md).

# 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.

{% hint style="warning" %}
The custom branch must already exist in the connected Git repository. Paradime does not create it for you.
{% endhint %}

***

#### 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
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.

{% hint style="info" %}
💡 **Note**: To update your schedules, merge (or push) your changes to the configured branch first. Commits to other branches are ignored.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.paradime.io/app-help/products/bolt/creating-schedules/schedules-as-code/deploying-yaml-schedules-from-a-custom-branch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.