From cb4fd95d7fe8db7be4a076dc902e24c4e45dce0d Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Wed, 11 Oct 2023 15:09:01 -0700 Subject: [PATCH] Add info about Azure --- .../release-notes/03-Oct-2023/custom-branch-fix-rn.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/custom-branch-fix-rn.md b/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/custom-branch-fix-rn.md index b3e0b60313a..06550b7d863 100644 --- a/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/custom-branch-fix-rn.md +++ b/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/custom-branch-fix-rn.md @@ -4,9 +4,11 @@ description: "October 2023: CI job runs now default to the main branch of the Gi sidebar_label: "Fix: Default behavior for CI job runs without a custom branch" tags: [Oct-2023, CI] date: 2023-10-06 -sidebar_position: 09 +sidebar_position: 08 --- If you don't set a [custom branch](/docs/dbt-cloud-environments#custom-branch-behavior) for your dbt Cloud environment, it now defaults to the default branch of your Git repository (for example, `main`). Previously, [CI jobs](/docs/deploy/ci-jobs) would run for pull requests (PRs) that were opened against _any branch_ or updated with new commits if the **Custom Branch** option wasn't set. +## Azure DevOps +Your Git pull requests (PRs) might not trigger against your default branch if you're using Azure DevOps and the default branch isn't `main` or `master`. To resolve this, [set up a custom branch](/faqs/Environments/custom-branch-settings) with the branch you want to target.