Fix: Default behavior for CI job runs without a custom branch

If you don't set a custom branch for your dbt Cloud environment, it now defaults to the default branch of your Git repository (for example, main). Previously, 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 with the branch you want to target.