Non-production branch builds, GitHub comments and preview URLs

src/content/docs/workers/ci-cd/builds/advanced-setups.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Advanced setups
 description: Learn how to use Workers Builds with more advanced setups
 sidebar:
-  order: 7
+  order: 8
 ---
 
 ## Monorepos
@@ -53,12 +53,12 @@ You can use [Wrangler Environments](/workers/wrangler/environments/) with Worker
 1. [Deploy via Wrangler](/workers/wrangler/commands/#deploy) to create the Workers for your environments on the Dashboard, if you do not already have them.
 2. Find the Workers for your environments. They are typically named `[name of Worker] - [environment name]`.
 3. Connect your repository to each of the Workers for your environment.
-4. In each of the Workers, edit your Wrangler deploy command to include the flag `--env: <environment name>` in the build configurations.
+4. In each of the Workers, edit your Wrangler commands to include the flag `--env: <environment name>` in the build configurations for both the deploy command, and the non-production branch deploy command ([if applicable](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds)).
 
 When a new commit is detected in the repository, a new build/deploy will trigger for each associated Worker.
 
 ### Example
 
 Imagine you have a Worker named `my-worker`, and you want to set up two environments `staging` and `production` set in the `wrangler.toml`. If you have not already, you can deploy `my-worker` for each environment using the commands `wrangler deploy --env staging` and `wrangler deploy --env production`.
 
-In your Cloudflare Dashboard, you should find the two Workers `my-worker-staging` and `my-worker-production`. Then, connect the Git repository for the Worker, `my-worker`, to both of the environment Workers. In the build configurations of each environment Worker, edit the deploy commands to be `npx wrangler deploy --env staging` and `npx wrangler deploy --env production` respectively.
+In your Cloudflare Dashboard, you should find the two Workers `my-worker-staging` and `my-worker-production`. Then, connect the Git repository for the Worker, `my-worker`, to both of the environment Workers. In the build configurations of each environment Worker, edit the deploy commands to be `npx wrangler deploy --env staging` and `npx wrangler deploy --env production` and the non-production branch deploy commands to be `npx wrangler versions upload --env staging` and `npx wrangler versions upload --env production` respectively.

src/content/docs/workers/ci-cd/builds/build-branches.mdx

@@ -0,0 +1,27 @@
+---
+pcx_content_type: concept
+title: Build branches
+description: Configure which git branches should trigger a Workers Build
+sidebar:
+  order: 6
+---
+
+When you connect a git repository to Workers, commits made on the production git branch will produce a Workers Build. If you want to take advantage of [preview URLs](/workers/configuration/previews/) and [pull request comments](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment), you can additionally enable "non-production branch builds" in order to trigger a build on all branches of your repository.
+
+## Change production branch
+
+To change the production branch of your project:
+
+1. In **Overview**, select your Workers project.
+2. Go to **Settings** > **Build** > **Branch control**. Workers will default to the default branch of your git repository, but this can be changed in the dropdown.
+
+Every push event made to this branch will trigger a build and execute the [build command](/workers/ci-cd/builds/configuration/#build-command), followed by the [deploy command](/workers/ci-cd/builds/configuration/#deploy-command).
+
+## Configure non-production branch builds
+
+To enable or disable non-production branch builds:
+
+1. In **Overview**, select your Workers project.
+2. Go to **Settings** > **Build** > **Branch control**. The checkbox allows you to enable or disable builds for non-production branches.
+
+When enabled, every push event made to a non-production branch will trigger a build and execute the [build command](/workers/ci-cd/builds/configuration/#build-command), follwed by the [non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command).

src/content/docs/workers/ci-cd/builds/build-watch-paths.mdx

@@ -3,7 +3,7 @@ pcx_content_type: concept
 title: Build watch paths
 description: Reduce compute for your monorepo by specifying paths for Workers Builds to skip
 sidebar:
-  order: 6
+  order: 7
 ---
 
 When you connect a git repository to Workers, by default a change to any file in the repository will trigger a build. You can configure Workers to include or exclude specific paths to specify if Workers should skip a build for a given path. This can be especially helpful if you are using a monorepo project structure and want to limit the amount of builds being kicked off.