azure-devops-docs VS azure-devops-dotnet-samples

An Azure DevOps repository has a default branch named "main" or "master". The default branch should be protected from code that doesn't build properly. As a best practice, set up a branch policy that requires all merges into the default branch to be performed with a pull request (PR). This policy provides two benefits. First, it prevents changes to the main branch directly. This helps to ensure code quality by requiring a code review before changes are merged into the default branch. Second, the PR forces a clean build of the merged code before it is merged. Branching and release strategies are important concepts to understand. To learn more see "Adopt a Git branching strategy". Branches and PRs can be managed via the Branches and Pull requests links, respectively.

As mentioned in this GitHub issue, there are no plans to deprecate Classic pipelines, you can use separate classic Build and Release Pipelines as you want. Refer to this blog for more info about Separating Build and Release Pipelines.

Glad to know that you fixed this issue. Refer to this document for more info.

When using an Azure DevOps pipeline to execute terraform code from a DevOps agent referencing an Azure Devops git Repo as a module source, we can make use of the Install SSH Key devops task to install the SSH key pair we just created onto the DevOps agent that will be executing the terraform code.

Hi, do you know if exist some possibility how to create PR via one of the .NET ADO libaries? Most similar packages is this - Microsoft.VisualStudio.Services.CodeReview.Client

Check this github issue for more info.

There are 780 outstanding issues on the docs repo though. Issues · MicrosoftDocs/azure-devops-docs (github.com)

I mean exactly this... https://github.com/MicrosoftDocs/azure-devops-docs/issues/5369 don't know it it's supported or not...

Hi, maybe you could check the sample here, try to get every member of the group using graphClient.ListMembershipsAsync(parentGroupDescriptor, Microsoft.VisualStudio.Services.Graph.GraphTraversalDirection.Down).Result;

Check the complete sample here.

Refer to .NET GitHub Repo for detailed samples.

Checked the samples here, cannot found any samples about test results. You can open an issue on GitHub to request a sample.

Hi, you can use Microsoft.TeamFoundationServer.Client, it provides access to version control, work item tracking, build, and more via public REST APIs. There are many samples on GitHub, check out the Git samples page.