Creando ramas y pull request

How to manage branches and pull requests in Azure DevOps?

Entering the world of software development can sometimes seem like a monumental challenge, especially when it comes to efficiently managing your source code in collaborative environments. Azure DevOps presents itself as an ideal tool to ease these processes, allowing developers to handle branches and pull requests efficiently. In this guide, we will take you through the process of creating branches and managing pull requests directly in Azure DevOps, thus optimizing your workflow in collaborative projects.

How to create a branch in Azure DevOps?

Branching is a vital part of the development cycle, allowing developers to work in parallel without interfering with each other's work. In Azure DevOps, creating a branch within the portal is an intuitive process.

1. Branches navigation: Go to the "Repos" section and select "Branches".
2. Identifying the repository: Make sure you are in the correct repository.
3. Branch Creation:
   • Select the base branch you want to start from (e.g. main or master).
   • Choose a clear and descriptive name for your new branch, avoiding spaces or special characters.
   • Optionally, associate the branch to a ProductBacklogItem, linking it to a specific ticket or task in the project for effective tracking.

Here's a basic example of what the workflow looks like using Azure DevOps:

git checkout -b NewBranch main

What are pull requests and how are they created?

A pull request is essentially a request to merge changes from one branch to another. This process not only ensures that new code complies with project standards, but also promotes peer review within the team.

1. Access pull requests: Go to the "Repos" section and select "Pull Requests".
2. Creating a new pull request:
   • Select the branch containing the changes(source branch) and the branch you want to merge those changes into(target branch).
   • Provide a clear title and detailed description for your pull request.
   • Assign reviewers from the team to make comments (a highly recommended practice in real projects to ensure code quality).
   • You can also tag the pull request or link it to an existing ticket.

The sample code for creating a pull request would look something like the following:

git push origin NewBranch# Create the pull request and specify the reviewer and additional details.

How are comments and approvals handled?

Managing comments is a crucial part of the pull request review process. Here is the procedure for interacting with comments:

• Reviewer assignment: reviewers can leave specific comments on chunks of code that need to be improved.
• Improvement annotations: If a reviewer suggests changes, the author of the pull request must reply and, if necessary, implement the necessary modifications.
• Review statuses: A pull request can be approved, rejected, or placed in a hold status until all outstanding comments are resolved.

Test your understanding

We encourage you to practice creating a new pull request to merge the changes found in the master branch to the new branch you previously created, e.g. AzureBranch. This will allow you to put into practice the concepts learned and solidify your understanding of how Azure DevOps facilitates the continuous flow of integration and development.

Remember, properly managing your branches and pull requests is essential for effective software development - keep exploring and improving your Azure DevOps skills!