--- title: What's new in Git 2.56.0? | daily.dev description: Git 2.56.0 has been released, bringing a new drop subcommand for git-history(1) to delete commits in one step, new --forked and --delete-merged flags for... canonical: https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: What's new in Git 2.56.0? | daily.dev og:description: Git 2.56.0 has been released, bringing a new drop subcommand for git-history(1) to delete commits in one step, new --forked and --delete-merged flags for... og:url: https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc og:image: https://api.daily.dev/og/posts/6QB5y6mSC.png og:image:alt: What's new in Git 2.56.0? og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # What's new in Git 2.56.0? **[GitLab](https://daily.dev/sources/gitlab)** · 13 min read · 1 upvotes · 0 comments ## Summary Git 2.56.0 has been released, bringing a new drop subcommand for git-history(1) to delete commits in one step, new --forked and --delete-merged flags for git-branch cleanup, and create/delete/update/rename subcommands for git-refs(1). It also adds a remote-object-info command for git-cat-file(1) to fetch object metadata without downloading blobs, a --drop-filtered option for git-repack(1) to reclaim disk space from partial clones, and a --linearize flag for git-replay(1) to handle merge commits during server-side rebases. The post also covers the roadmap toward Git 3.0, with an interim 2.98 release planned for December 2026 and 2.99/3.0 shipping together in spring 2027, largely driven by SHA-256 and Rust ecosystem readiness. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What new subcommand did git-history(1) get in Git 2.56.0 for deleting commits? Git 2.56.0 adds a drop subcommand to git-history(1), letting you delete a commit with a single command instead of an interactive rebase. Running git history drop removes the commit and rebases its descendants onto its parent, updating all branches descended from the original commit to point to the rewritten history. _daily.dev helps developers track new Git commands like this as they ship across releases._ ### How can I delete Git branches that were merged into origin/main but not detected by git branch --merged? Git 2.56.0 adds a --delete-merged flag to git branch that deletes branches whose tips are reachable from their configured upstream, catching branches merged into origin/main even if they weren't merged directly into the local main. A companion --forked flag lists branches whose upstream matches a given ref, remote, or branch, useful for auditing feature branches before cleanup. _Track Git workflow improvements like branch cleanup flags as you plan upgrades on daily.dev._ ### When is Git 3.0 planned to be released and what breaking changes does it include? Git 3.0 is scheduled to ship together with Git 2.99 in spring 2027, following an interim 2.98 release in December 2026 that signals the upcoming breaking changes to downstream maintainers. Git 3.0 will flip a breaking-changes feature flag while keeping feature parity with 2.99; 2.99 will be an LTS release for platforms lacking a Rust toolchain, and SHA-256 support readiness across forges is a key driver of the timeline. _Developers planning a Git 3.0 migration can follow roadmap changes like this on daily.dev._ ## Similar posts on daily.dev - [Looking forward to Git 2.56 - and 3.0](https://daily.dev/posts/looking-forward-to-git-2-56---and-3-0-h3in0tamj) · Lobsters · 3 upvotes · 2 comments - [Highlights from Git 2.52](https://daily.dev/posts/highlights-from-git-2-52-4qkhhmx3p) · GitHub Blog · 98 upvotes · 1 comments - [Git 2.56-rc0 Released With Updated Contribution Guidelines, Improvements For Swift](https://daily.dev/posts/git-2-56-rc0-released-with-updated-contribution-guidelines-improvements-for-swift-ycuj0vo5e) · Phoronix · 0 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#git](https://daily.dev/tags/git), [#version-control](https://daily.dev/tags/version-control), [#gitlab](https://daily.dev/tags/gitlab) [View this post on daily.dev](https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"What's new in Git 2.56.0?","url":"https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc"},"datePublished":"2026-09-28T18:10:09.567Z","dateModified":"2026-09-28T18:11:09.248Z","description":"Git 2.56.0 has been released, bringing a new drop subcommand for git-history(1) to delete commits in one step, new --forked and --delete-merged flags for...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3fdfe93a6c1863f84c038a3922dfbe78?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3fdfe93a6c1863f84c038a3922dfbe78?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitLab","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitLab","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3720ce340ca4435daef529abbf361b69","url":"https://daily.dev/sources/gitlab"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,git,version-control,gitlab","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitLab","item":"https://daily.dev/sources/gitlab"},{"@type":"ListItem","position":3,"name":"What's new in Git 2.56.0?"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-s-new-in-git-2-56-0--6qb5y6msc#faq","mainEntity":[{"@type":"Question","name":"What new subcommand did git-history(1) get in Git 2.56.0 for deleting commits?","acceptedAnswer":{"@type":"Answer","text":"Git 2.56.0 adds a drop subcommand to git-history(1), letting you delete a commit with a single command instead of an interactive rebase. Running git history drop removes the commit and rebases its descendants onto its parent, updating all branches descended from the original commit to point to the rewritten history. daily.dev helps developers track new Git commands like this as they ship across releases."}},{"@type":"Question","name":"How can I delete Git branches that were merged into origin/main but not detected by git branch --merged?","acceptedAnswer":{"@type":"Answer","text":"Git 2.56.0 adds a --delete-merged flag to git branch that deletes branches whose tips are reachable from their configured upstream, catching branches merged into origin/main even if they weren't merged directly into the local main. A companion --forked flag lists branches whose upstream matches a given ref, remote, or branch, useful for auditing feature branches before cleanup. Track Git workflow improvements like branch cleanup flags as you plan upgrades on daily.dev."}},{"@type":"Question","name":"When is Git 3.0 planned to be released and what breaking changes does it include?","acceptedAnswer":{"@type":"Answer","text":"Git 3.0 is scheduled to ship together with Git 2.99 in spring 2027, following an interim 2.98 release in December 2026 that signals the upcoming breaking changes to downstream maintainers. Git 3.0 will flip a breaking-changes feature flag while keeping feature parity with 2.99; 2.99 will be an LTS release for platforms lacking a Rust toolchain, and SHA-256 support readiness across forges is a key driver of the timeline. Developers planning a Git 3.0 migration can follow roadmap changes like this on daily.dev."}}]} ```