DevOps now supports creating pull requests, forking code repositories and provides critical code repository insights

Using the Pull Request (PR) feature, developers can now seamlessly collaborate on new code changes by raising a PR and adding reviewers who can provide feedback and approve the code changes. Users can also set personalized notification preferences at the pull request, repository, or project level to receive relevant updates on PR events. Repository admins can protect important branches by using the branch protection feature and ensure compliance by requiring a minimum approval count and enforcing a successful build before merging a PR. Finally, the pull request event can be used to trigger an automate build and deployment of the new code changes. For more information, see Managing Pull Requests.

Forking is a popular software development pattern where an independent copy of the original repository is created in a separate project space. Using the Repository Fork feature, developers can now suggest improvements and modifications without directly modifying the original repository or requiring higher access privileges. After the suggested modifications are ready to be submitted, the developer can create a pull request from their forked repository to the original repository enabling them to comply with the merge enforcements of the original repository. For more information, see Forking a Code Repository.

The Repository Insights feature captures and visualizes data to help development teams analyze the frequency of code changes, monitor code review times, and track code contributions. Using this feature, developers and managers can get an overview of repository activity in terms of the number of commits and pull requests, view code frequency data, analyze code review times, and view contribution metrics such as pull requests created, commented or reviewed. For more information, see Code Repository Insights.