demo

Author: Rami Bououni

docs/pipelines/release/deploy-multiple-branches.md

@@ -36,6 +36,8 @@ In this section, you create the base Classic release pipeline and configure the
 
 1. Under **Stages**, select the default stage and rename it to **Dev**. In the next steps, you configure this stage to deploy only when an artifact is produced from the *Dev* branch.
 
+    :::image type="content" source="media/rename-stage-classic-release.png" alt-text="A screenshot displaying how to rename a stage in a Classic release pipeline.":::
+
 1. Under **Artifacts**, select **Add**.
 
 1. Configure the artifact source:
@@ -44,8 +46,12 @@ In this section, you create the base Classic release pipeline and configure the
     - Complete the required fields for that source type, such as project, pipeline, and default version.
     - Select **Add**.
 
+    :::image type="content" source="media/add-artifact-to-classic-release.png" alt-text="A screenshot that shows how to add an artifact to a Classic release pipeline.":::
+
 1. Select the **Continuous deployment trigger** icon on the artifact, and then turn on **Continuous deployment trigger** to create a release whenever a new artifact is available.
 
+    :::image type="content" source="media/enable-continuous-deployment-trigger.png" alt-text="A screenshot displaying how to enable the continuous deployment trigger in a Classic relealse pipeline.":::
+
 1. In the **Dev** stage, select the **Pre-deployment conditions** icon.
 
 1. Set **Deployment trigger** to **After release** so the stage starts automatically whenever a new release is created.
@@ -59,6 +65,9 @@ In this section, you create the base Classic release pipeline and configure the
 
     With this filter in place, the **Dev** stage deploys only when the release is created from a build of the *Dev* branch.
 
+    :::image type="content" source="media/add-predeployment-conditions-to-classic-release.png" alt-text="A screenshot displaying how to set up the pre-deployment conditions in a Classic release pipeline.":::
+
+
 ## Add a new stage
 
 In this section, you add a second stage (**Prod**) to the same release pipeline and configure it to deploy only when artifacts are built from the *main* branch. This lets you keep branch-to-stage routing consistent across environments.
@@ -86,6 +95,8 @@ In this section, you add a second stage (**Prod**) to the same release pipeline
 
     With this filter in place, the **Prod** stage deploys only when the release is created from a build of the *main* branch.
 
+    :::image type="content" source="media/add-predeployment-conditions-to-classic-release-prod-stage.png" alt-text="A screenshot displaying how to configure the predeployment conditions for the Prod stage in a Classic release pipeline.":::  
+
 ## Deploy to a specific stage
 
 At this point, your release pipeline is configured to route deployments by branch: artifacts from the *Dev* branch deploy to the **Dev** stage, and artifacts from the *main* branch deploy to the **Prod** stage. Use the following checks to validate that the branch filters are working as expected.