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 ✌️
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
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.
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 ?
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!
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.