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

[@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 Subscribe WebGentle: goo.gl/PJr1pN Visit Our Website: www.webgentle.com Visit WebGentle Community: www.webgentle.com/community Do like the video and subscribe to the channel ✌️

[@akashgupta2366]

Great tutorial for PR concepts thanks

[@aliqureshi7171]

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

[@EliteCycleWalkWindsorCanada]

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

[@shivprasadgurjar487]

Very good explanation

[@uditbhatia4127]

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 ?

[@arvindvs8934]

Wonderful explanation. Thank you sir!!

[@WebGentle]

Keep watching

[@raghavenderrao4197]

Superb explanation sir thank you.

[@felipecapelli2665]

Thank you for sharing this content =)

[@mukhaidbashakhan7936]

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

[@shubhamdevdas8313]

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

[@zeetsoft]

Thank you so much for sharing it.

[@anuragmohanty9329]

Awesome Sir

[@nkosinathiradebe9069]

Beautiful. Thank you.

[@juliestudy1475]

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!

[@WebGentle]

Yes. Creating a feature branch and using pull request for code review is always recommended. You can restrict access (writing to master branch, min 2 reviewer, etc) by using policies.

[@zafarahmad1356]

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.

[@kidzcode8027]

can you show how to automate the create a pull request?

[@kieranpatel2192]

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

[@karthik.c8892]

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

[@harshavardhan9991]

Thank you !!

[@kapa2220]

But developers can still make Push to master from Visual Studio etc. without raising a pull request. So how to handle that?

[@ericfleet9602]

That's where you create branch policies to prevent that.

[@sirishagandla5553]

Thanks

[@chaitramadhu7329]

Can we merge two branches which belongs to different repositories?

[@WebGentle]

In general terms one repository represents one project. Then what is the purpose of merging two different projects together?

[@chaitramadhu7329]

@@WebGentle If two projects are serving same purpose? Can we?

[@WebGentle]

If they are serving same purpose then why they are 2?

[@chaitramadhu7329]

@@WebGentle So, you mean to say, it's of no use?

[@WebGentle]

Yes. We can not merge branches from different repo. And ideally there should be same code in multiple repo

[@FlorjonKoci]

helpful

[@edurodriguez29]

It's really hard to understand you, (What you say)

[@nethmagunathilaka]

Watch from the beginning