Edit

Azure Repos - Sprint 273 Update

Features

Improvements to pull request status checks

We added a new External badge to pull request status checks to help you distinguish custom third-party status policies from built-in Azure DevOps branch policies. Previously, external policies looked identical to standard policies like builds or required reviewers, which often caused confusion when a pull request was blocked.

With this update, external status policies are now clearly labeled in the checks experience, and hovering over the badge provides additional details about the policy owner and that it's managed outside of standard branch policies. This helps authors and reviewers quickly understand why a pull request is blocked and resolve issues faster.

Screenshot showing the new External badge on a pull request status check.

Show unresolved comments on pull request list

We now highlight pull requests that contain unresolved comment threads directly in the pull request list view.

This gives authors and reviewers quick visibility into whether a pull request still needs attention before it can be completed or merged. Instead of opening each pull request to check discussion status, you can immediately see if there are outstanding review comments that still need to be addressed.

The unresolved comment indicator displays the number of unresolved threads alongside the total number of comment threads (for example, 1 / 3), making it easier to understand review progress at a glance.

Screenshot showing the unresolved comments indicator on the pull request list.

Git object count limit removed

The hard limit on the number of Git objects in a repository has been removed. Previously, repositories were capped at 100 million objects, which could be a constraint for very large and active codebases. With this change, repositories can grow without an object count ceiling, improving scalability and longevity.

This especially benefits long-lived, large monorepos with extensive history, a huge number of contributors, and continuous development at scale.

Next steps

Note

These features will roll out over the next two to three weeks.

Head over to Azure DevOps and take a look.

How to provide feedback

We would love to hear what you think about these features. Use the help menu to report a problem or provide a suggestion.

Make a suggestion

You can also get advice and your questions answered by the community on Stack Overflow.