{
  "id": 10895399,
  "title": "Git 2.56 Takes Aim at Messy Merges, Slow Diffs and Branch Sprawl",
  "url": "https://urgent.news/2026/09/30/git-2-56-takes-aim-at-messy-merges-slow-diffs-and-branch-sprawl",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-30T07:53:51.000Z",
  "source": {
    "name": "DevOps.com",
    "slug": "devops-com",
    "url": "https://devops.com/git-2-56-takes-aim-at-messy-merges-slow-diffs-and-branch-sprawl/"
  },
  "original_language": "en",
  "account": "Git 2.56 aims to tackle common issues that developers encounter, such as messy merges, slow diffs, and branch sprawl. This release, developed by 104 contributors, includes several improvements that impact both performance and user experience.\n\nOne notable addition is the git add --resolved option, which helps resolve merge conflicts by only considering paths that are currently unmerged in the index. It scans the files for leftover conflict markers before staging anything, preventing users from accidentally staging the wrong changes. This small feature provides a much-needed safety net for developers who have pushed changes into shared branches.\n\nPerformance improvements are a key focus of this release. For example, Git now finds merge bases more efficiently by ending history traversal earlier once it has the required information. In the Linux kernel, the git merge-base --all command experienced a significant reduction in traversal steps and execution time. Additionally, path-limited working-tree diffs have been optimized, cutting the time required for such operations in large repositories from minutes to seconds.\n\nThe new path-walk repacking feature offers substantial storage efficiency improvements. In the Fluent UI repository, ordinary bitmapped repacking produced a smaller pack size compared to the traditional approach. Partial clone users also benefit from a new --drop-filtered option for git repack, which enables teams to remove specific blobs based on filters, such as files exceeding a certain size, and fetch them on demand when needed.\n\nOther enhancements include more control for partial clone users through the --drop-filtered option in git repack, git branch --delete-merged for cleaning up merged branches, and a --reset-when-found option in git bisect run for efficient bug tracking. The consolidated git refs command simplifies low-level reference operations, and experimental commands like git history drop and git replay --linearize aim to make history editing easier.\n\nFinally, Git 2.56 introduces safety features that address the increasing adoption of AI coding agents. For instance, staged conflict markers are refused staging, and the new git history drop command removes selected commits and replays their descendants onto their parent without touching unrelated local changes. These safety options are crucial for agent workflows, providing guardrails against potential issues.\n\nOverall, Git 2.56 offers a range of performance enhancements and safety features that cater to both human developers and AI coding agents. It is essential for teams to ensure their build agents, developer workstations, and hosting platforms are running the updated version to fully benefit from these improvements.",
  "summary": "Git 2.56 improves merge safety, speeds up large-repository operations and adds cleanup tools that could prove especially useful for AI coding agents and busy DevOps teams.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}