In previous posts I’ve talked about performance improvements that our team contributed to the Git community. At Microsoft, we’ve been pushing Git to its limits with the largest and busiest Git repositories on the planet, improving core Git as we go and sending these improvements back upstream.
Today, we are enabling developers to sign in with their existing GitHub account to Microsoft online services, on any Microsoft log in page. Using your GitHub credentials, you can now sign in via OAuth anywhere a personal Microsoft account does, including Azure DevOps and Azure.
While you’ve been able to get started with Azure Boards from azure.com/boards for several months now, the new app in the GitHub Marketplace streamlines the acquisition of the service and configuration of your GitHub repository connections.
Today, we are announcing new features for Azure Pipelines, including multi-stage YAML pipelines (for CI and CD), environments and deployment strategies, and Kubernetes support.
We are announcing new features features designed to help our customers build applications with Docker containers and deploy them to Kubernetes clusters, on all cloud providers and on-premises.
We are making a change to Azure DevOps to block the harmful flatmap-stream 0.1.0 package and the versions of event-stream newer than version 3.3.4 which make use of the flatmap-stream package.
With the Azure DevOps Sprint 143 Update, we’re excited to announce the availability of our new rich text editor on the work item form in Azure Boards. The work item form can be accessed in Azure Boards from the work items hub,
We’ve been discussing the commit-graph feature in Git 2.18 and how we can use generation numbers to accelerate commit walks. One area where we can get significant speedup is when presenting output in topological order. This allows us to walk a much smaller list of commits than before.
Earlier, we announced that Git 2.18 contains a new commit-graph feature, and we discussed the commit-graph file format. As shipped in Git 2.18, this file only speeds up commit walks by a constant multiple, due to parsing structured data from the commit-graph file.
Earlier, we announced the commit-graph feature in Git 2.18 and talked about some of its performance benefits. Today, we’ll discuss some if the technical details about how the commit-graph feature works, including some helpful properties of its file format. This file speeds up commit-graph walks so much that we were able to identify other ways to speed up these walks using small optimizations.