News

Visual Studio Team Services Sprint 113 Improves PR Experience

Another month, another VSTS sprint. This one features a number of team-related pull request improvements and a more efficient package management UI.

Microsoft's Visual Studio team continues on with the next sprint release, number 113, of Visual Studio Team Services. This one mainly sports pull request and package management improvements, but there's also a number of other useful features being rolled out on the Web in the next few weeks.

"There's a bunch of nice improvements to the Pull Request experience – we continue to refine and evolve it," writes Microsoft's Brian Harry, in a blog post announcing the sprint last week. "We also did a "V2" overhaul of the package management UI."

Among the PR improvements is a streamlining of team notifications. It's in preview mode for now, but what happens is upon creation of a PR, an e-mail notification is automatically generated and sent to team members assigned to it. Afterward, PR updates will also generate an email to team members. Team notifications will also be available in the future for PRs meant for Azure Active Directory groups and teams that are part of AAD groups, according to the release notes.

Other PR improvements: fine-tune branch policy call to actions for PR authors and reviewers, and better resolving and filtering of comments within a PR; PR details view includes an Update tab that now shows force push and rebase changes; advanced filtering options for commit history results; trigger for GitHub-based PR builds (only works when source and target are on same repo, not forked ones).

The package management UI improvements that Harry also cites mainly have to do with performance. "We've updated the Package Management user experience to make it faster, address common user-reported issues, and make room for upcoming package lifecycle features," writes Jamie Cool, a VSTS Group Program Manager, in the release note.

Outside of those highlighted features are improvements to agent allocation and selection, automated test capabilities in the VS Test task, ability to create multiple task versions for custom extensions, and a cleanup feature for agent pools. For details on these, check out the release notes for VSTS Sprint 113 here.

About the Author

Michael Domingo is a long-time software publishing veteran, having started up and managed several developer publications for the Clipper compiler, Microsoft Access, and Visual Basic. He's also managed IT pubs for 1105 Media, including Microsoft Certified Professional Magazine and Virtualization Review before landing his current gig as Visual Studio Magazine Editor in Chief. Besides his publishing life, he's a professional photographer, whose work can be found by Googling domingophoto.

comments powered by Disqus

Featured

  • Creating Reactive Applications in .NET

    In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

  • .NET 9 Preview 3: 'I've Been Waiting 9 Years for This API!'

    Microsoft's third preview of .NET 9 sees a lot of minor tweaks and fixes with no earth-shaking new functionality, but little things can be important to individual developers.

  • Data Anomaly Detection Using a Neural Autoencoder with C#

    Dr. James McCaffrey of Microsoft Research tackles the process of examining a set of source data to find data items that are different in some way from the majority of the source items.

Subscribe on YouTube