{"id":11021,"date":"2016-01-20T05:00:00","date_gmt":"2016-01-20T05:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2016\/01\/20\/pull-request-improvements-in-visual-studio-team-services-2\/"},"modified":"2022-08-03T00:16:21","modified_gmt":"2022-08-03T08:16:21","slug":"pull-request-improvements-in-visual-studio-team-services-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/pull-request-improvements-in-visual-studio-team-services-2\/","title":{"rendered":"Pull Request Improvements in Visual Studio Team Services"},"content":{"rendered":"

Code Review with pull request is a central part of every git developer’s inner loop.\u00a0 Over the past few months, we’ve added a number of improvements to the pull request web experience for Visual Studio Team Services (VSTS), all focused on improving productivity while using pull requests.\u00a0 Let’s take a look at what’s new.<\/p>\n

Personalized Pull Request Hub<\/h2>\n

The pull request hub is the starting point for both creating PRs and finding PRs that need reviewed.\u00a0 To make it easier for developers to find the PRs that need their input, we’ve reorganized the hub to put the most important PRs in focus.\u00a0 The first two sections are self-explanatory: requested by me, and assigned to me.\u00a0 The third section shows any PR that’s been assigned to the team that’s selected in the project\/team picker.\u00a0<\/p>\n

\"\"<\/p>\n

For each pull request, a rollup of the status is shown to highlight the PRs that require action.\u00a0<\/p>\n

\"\"<\/p>\n

Reviewers are shown with an overlay of their votes, to help identify at a glance which teams and users have signed off.<\/p>\n

\"\"<\/p>\n

The “All” view provides a way to find pull requests that don\u2019t appear in your default view.\u00a0 Currently, there are some canned filter options, and coming soon we’ll be providing richer options to filter PRs by author and reviewer.<\/p>\n

\"\"<\/p>\n

Streamlined Discussions<\/h2>\n

The discussions view provides a summary of the activity on a pull request, but in PRs with a lot of comments and multiple reviewers, the summary can be quite busy.\u00a0 To help reviewers focus on the most important details, there are now options to show only comments, or further scope down the view to show only comments left on the discussion (and not in the files).<\/p>\n

\"\"<\/p>\n

Related Work Items<\/h2>\n

VSTS has always been about integration between code, builds, and work items, and now we’ve brought that integration to pull requests.\u00a0 The Related Work Items section makes it simple to link PRs to bugs and stories, providing context to reviewers that might need a little more detail.\u00a0<\/p>\n

\"\"<\/p>\n

Just enter an ID or keyword to find the work item you want to link.<\/p>\n

\u00a0\"\"<\/p>\n

A Better Merge Experience<\/h2>\n

After all of the votes are in and your build is passing, it’s time to complete your PR.\u00a0 The merge dialog provides an opportunity to customize the merge commit message, taking the defaults from the PR title and description.\u00a0 To keep your repos clean, check the option to delete the source branch when the merge is complete.\u00a0 Coming soon is an option to squash when merging, keeping the history graph simple and free of merge commits.<\/p>\n

\"\"<\/p>\n

After the merge is complete, the merge commit will be automatically linked to the related work items, keeping the traceability in place from the code to the work items.\u00a0<\/p>\n

These features are just the beginning of some larger investments we have underway for pull requests, so stay tuned for more updates in the coming months. \u00a0In the meantime,\u00a0go to your account to try out the new features<\/span><\/a><\/span>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Code Review with pull request is a central part of every git developer’s inner loop.\u00a0 Over the past few months, we’ve added a number of improvements to the pull request web experience for Visual Studio Team Services (VSTS), all focused on improving productivity while using pull requests.\u00a0 Let’s take a look at what’s new. Personalized […]<\/p>\n","protected":false},"author":198,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,225],"tags":[],"class_list":["post-11021","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-git"],"acf":[],"blog_post_summary":"

Code Review with pull request is a central part of every git developer’s inner loop.\u00a0 Over the past few months, we’ve added a number of improvements to the pull request web experience for Visual Studio Team Services (VSTS), all focused on improving productivity while using pull requests.\u00a0 Let’s take a look at what’s new. Personalized […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/11021","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/198"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=11021"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/11021\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=11021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=11021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=11021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}