Cherry-pick a pull request
To copy changes made in a pull request to another branch in your repo, follow these steps:
* In a completed pull request,select Cherry-pick, or for an active pull request, select Cherry-pick from the
... menu. Cherry-picking a pull request in this way creates a new branch with the copied changes. Merge into a target branch in a second pull request.
* In Target branch, enter the branch you want to merge the copied changes.
* In Topic branch name, enter a new branch to contain the copied changes, then select Cherry-pick.
* Select Create pull request to merge the topic branch into the target branch to complete the cherry-pick.
nce:
https://docs.microsoft.com/en-us/azure/devops/repos/git/pull-requests

Explanation:
A screenshot of a computer AI-generated content may be incorrect.

Explanation:

Box 1: Azure Container Registry
Azure services like Azure Container Registry(ACR) and Azure Container Instances (ACI) can be used and connected from independent container orchestrators like kubernetes (k8s). You can set up a custom ACR and connect it to an existing k8s cluster to ensure images will be pulled from the private container registry instead of the public docker hub.
Box 2: An Azure service principal
When you're using Azure Container Registry (ACR) with Azure Kubernetes Service (AKS), an authentication mechanism needs to be established. You can set up AKS and ACR integration during the initial creation of your AKS cluster. To allow an AKS cluster to interact with ACR, an Azure Active Directory service principal is used.
References:
https://thorsten-hans.com/how-to-use-private-azure-container-registry-with-kubernetes
https://docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration

See explanation below
Explanation:
Task 9: Initialize the main branch (if it doesn't exist) and create a pull request-triggered pipeline for .
NET Core build
Step 1: Initialize the main Branch
* In your Azure DevOps Project (Project1), navigate to Repos.
* In the left menu, click Files.
* If you see a message like "This repository is empty," click Initialize.
* Create a README.md file (or another file) and set the default branch name to main.
* Click Initialize.
If the main branch already exists, you can skip this step.
Step 2: Create a New Branch for the Pipeline
* In Repos > Files, click on the Branches tab.
* Click New branch.
* Enter:
* Branch name: azure-pipelinesT
* Based on: main
* Click Create.
This creates a new branch named azure-pipelinesT from main.
Step 3: Create the Pipeline YAML File in the New Branch
* Switch to the azure-pipelinesT branch.
* In Files, click New file.
* Name the file: azure-pipelines.yml.
Step 4: Write the YAML Pipeline for .NET Core Build
Here's a sample YAML file:
trigger: none
pr:
branches:
include:
- main
pool:
vmImage: 'windows-latest'
variables:
buildConfiguration: 'Release'
steps:
- task: UseDotNet@2
displayName: 'Install .NET Core SDK'
inputs:
packageType: 'sdk'
version: '8.x' # Or specify the exact version of .NET Core SDK you need installationPath: $(Agent.ToolsDirectory)/dotnet
- script: dotnet build src --configuration $(buildConfiguration)
displayName: 'Build .NET Core project'
This pipeline:
* Runs only when a pull request is created or updated targeting the main branch.
* Uses the windows-latest agent.
* Installs the .NET SDK and builds the project in the src directory.
Step 5: Commit the Pipeline File
* In the bottom commit message box:
* Message: Add PR-triggered pipeline for .NET Core build
* Ensure the branch is set to azure-pipelinesT.
* Click Commit.
Step 6: Create the Pipeline in Azure DevOps
* In the left menu, click Pipelines.
* Click New pipeline.
* Select:
* Azure Repos Git.
* Select your repository.
* Choose Existing Azure Pipelines YAML file.
* In the branch selector, choose the azure-pipelinesT branch.
* Select the YAML file path (azure-pipelines.yml).
* Click Continue and Run to validate.
Step 7: Test the Pipeline Trigger
* Create a new branch (e.g., feature/test-pr).
* Push a commit and create a pull request targeting main.
* Verify that the pipeline runs automatically for this PR in Pipelines.