proomt

Search

Search posts, papers, and topics

All posts

LWN.netjake51 min readrelease notesintermediate

Git v2.56.0 released

Read on lwn.net

Summary

Git v2.56.0 has been released, featuring 748 non-merge commits from 104 developers. Key updates include a safer conflict resolution workflow, a new `git history drop` subcommand, and smaller path-walk repacks, alongside various usability and performance enhancements.

  • `git add --resolved` stages conflict-resolved paths, leaving unrelated local changes unstaged.
  • `git history drop` subcommand removes a commit and replays its descendants onto its parent.
  • `git bisect --reset-when-found` automatically resets to the original state or the found culprit.
  • `git branch --delete-merged` removes local branches already merged into their tracked remote-tracking branches.

This release offers significant quality-of-life improvements and new capabilities for all Git users, particularly those managing complex repositories, large histories, or partial clones.

6/10
devopscliperformancegitworkflowversion control

Related reading

  1. Reinventing issue tracking: Local-first and Git-native

    A devlog describing how Manganin’s issue tracker stores issues in a dedicated Git repo as plain files, after rejecting earlier approaches that tried to embed issue data in the code tree or Git refs. The author explains the pitfalls of using refs for issue storage, shows the low‑level Git commands needed for that approach, and then outlines the final design: a hidden sister repository where each i…

    Lobstersmanganin.dev6 minHN1lobste.rs27

  2. MozPhab 2.17.0 Released

    MozPhab 2.17.0 has been released, addressing three bugs. Key improvements include parallelizing per-commit upload and creatediff, and skipping unnecessary git checkout restoration.

    Mozilla Automation Teammozilla.org1 minrelease

  3. Migrating Repositories to Git 3.0: Moving to SHA-256 and Reftables

    The article outlines a step‑by‑step workflow for migrating existing Git repositories to the new SHA‑256 object format and reftable reference backend, including an audit script, conversion commands, and rollback guidance. Following the guide lets teams modernize their repos, improve scalability and address SHA‑1 security concerns.

    SitePointsitepoint.com17 min

  5. Developer policy update: Transparency, state policy, and what’s ahead

    GitHub updated its transparency reporting, showing a significant increase in government takedown requests due to revised counting methods, not more content removals. The company also detailed its engagement in 2026 state legislative sessions, influencing AI transparency and age assurance laws to protect open source projects from unintended impacts.

    GitHub Oldgithub.blog5 min