What's new with Azure Repos? - Azure DevOps Blog
Briefly

What's new with Azure Repos? - Azure DevOps Blog
"We thought it was a good time to check in and highlight some of the work happening in Azure Repos. In this post, we've covered several recent improvements, along with a preview of features that are coming soon. To stay up to date, be sure to visit the Azure DevOps Roadmap. These changes have either already been released or are currently rolling out. Be sure to check the sprint release notes for full details."
"Over the past year, we've been guiding customers through migrating existing, obsolete policies to the new storage format and preventing the creation of new ones using the old model. With this release, any remaining check-in policies still using the obsolete format will be disabled. These policies will no longer function, and you'll need to migrate them to the new format for check-in policies to continue working."
"Improved Comment Navigation from Pull Request Links We've made improvements to how Azure DevOps handles deep links to pull request comments. When opening a pull request from a direct comment link, focus is now handled more reliably, especially for pull requests with a large number of comments. This makes it easier to jump directly to the feedback you care about without losing context."
Azure Repos has released and is rolling out several improvements and previews. Some updates require action: obsolete TFVC check-in policies stored in the old format will be disabled and must be migrated to the new storage format for check-in policies to continue functioning. Guidance and step-by-step migration resources were published earlier. Deep links to pull request comments now focus reliably, improving navigation especially in pull requests with many comments. Email notifications for pull requests were updated to reduce noise and remove low-value messages such as draft state changes and auto-complete updates. Users should consult the Azure DevOps Roadmap and sprint release notes for details.
Read at Azure DevOps Blog
Unable to calculate read time
[
|
]