(#36) How to create Pull Request in azure devops | Azure devops tutorial for beginners

Показать описание

Azure DevOps Tutorial: In this video, we will learn about Pull Request in Azure DevOps.
When we work on multiple branches in the azure repo and our work is done in the child branch. Then, to publish the code on production we need to merge the child branch code to the master branch. Since we always treat the master branch as a production-ready branch hence there should not be any false code in the master branch.
Instead of direct merging the child code to the master branch we create a Pull Request.

A pull request is a mechanism to merge a branch to other with some additional features.
A pull request is used to :
# Merge a branch code to another branch.
# Code review.
# Add reviewers to review the pull request.
# Associate work item to pull request.
# And lots more...

Timestamp
# Need of Pull Request 00:50
# What is a pull request 01:31
# How to create pull request 02:06
# Add reviewer in pull request 04:25
# Associate work item to pull request 05:14
# Validate the code changes in pull request 05:34
# Approve the pull request 10:02
# Complete the (merging) pull request 10:56

#AzureDevOps #PullRequestInAzureDevops #AzureDevOpsTutorial

Follow us on
==========

Popular free courses from WebGentle
=========

Рекомендации по теме

Комментарии

Timestamp
# Need of Pull Request 00:50
# What is a pull request 01:31
# How to create pull request 02:06
# Add reviewer in pull request 04:25
# Associate work item to pull request 05:14
# Validate the code changes in pull request 05:34
# Approve the pull request 10:02
# Complete the (merging) pull request 10:56

#AzureDevOps #PullRequestInAzureDevops #AzureDevOpsTutorial

Do like the video and subscribe to the channel ✌️

WebGentle

Cool and amazing feature pull request organize way, feature will help developer and team member working on it, sample ample of communication time using Repo-pull feature, fantastic explanation, Ty bro Nitish K. bhai

aliqureshi

Great videos. Thanks for posting and your hardwork. Greetings from Pakistan.

EliteCycleWalkWindsorCanada

Wonderful explanation. Thank you sir!!

arvindvs

When you added a line changes and then there will be a conflict but we need to resolve that conflict means we need to add that in our master branch but you deleted that and added a new line Update then the conflict will resolved how ?
At that time why conflict didn’t come ?

uditbhatia

If i join will i learn everything about pipelines in azure ? i like your teachings.

kieranpatel

Hi Nitish it's a great tutorial I just need to ask one question that when customizing the Inherited process I see there are hierarchies like Epic -> Issue -> Task and when we create new work items for example Model Work, Controller Work, UI Work and we want to set it under task, for example, Epic -> Issue -> Task -> Login Process -> Model Work can we do that here Login Process is a Task and I want to subdivide it into three areas Model, Controller, and View(UI). Kindly clear this concept and I'll be grateful to you you have already made a big contribution to the community Thanks a Lot.

zafarahmad

Why did the " //changes " created a conflict ? and why you removed that ?

shubhamdevdas

Hi Nitish you videos are very good
Thank you
can you make a video on how to use PowerShell script task in azure devops during pipeline build

karthik.c

Am trying to push the branch getting this message - fatal POClocal can not be resolved to branch. Can you please help me to understand?

mukhaidbashakhan

Is it best practice to always use a branch and use the pull request to force an approval process? Otherwise, it seems anyone can just submit directly to the master branch. Can it be set up that a particular member can only work on a particular branch and can't submit directly to the Master branch? ie must use a pull request? Many thanks!

juliestudy