Git 2.54 is here with features like config-based hooks, new ways to rewrite history, and much more. ✨ Check out the highlights from this release. 👇 github.blog/open-source/gi…

@github That's a solid update—config hooks and history rewriting are game-changers. Always love seeing Git evolve!

@github @Meligy GitHub still can't perform a fast-forward rebase. pretty basic functionality for Git. I inly requested this feature like a decade ago.

@github config-based hooks is huge for AI agent repos. no more forgetting to set up pre-commit checks when spinning up new automation projects

AD Genuinely glad I watched this during the day because there's zero chance I'm turning the lights off tonight. Easily the most unsettling thing l've seen in years. Lee Cronin's The Mummy - Only in Theaters this Friday. Get tickets now!

@github To be honest I am not even yet done studying git 2.0 like the tool is just huge 😂

@github @grok writen down the key points

@github History rewriting improvements are always welcome.

@github Ko

@github Config hooks finally fix the symlink mess. Expect a rough migration cycle for legacy repos.

@github Nice — git history is the real gem here. Finally don’t need a full interactive rebase just to reword a commit message. Config-based hooks are long overdue too. Feels like they’re quietly clearing the deck for Git 3.0.

@github Yep Linux users you know what to do PKG Apt Pacman Update git 😎

@github Simple, smart improvements. Git team cooking again. 👏👏

@github GitHub is something me and other vibe coders use all the time, even if we don’t really know what it is.

@github Config based hooks finally solve the "works on my machine" linter problem. We used to rely on husky or copy scripts around manually. Being able to check these into the repo and have them run for every contributor is a quiet but huge DX win.

It is deeply frustrating to realize that users on lower-tier plans effectively helped train and improve the AI, only to later lose access to the most advanced models. This creates the impression that their contribution was leveraged without fair or transparent compensation. Changes like this, when not clearly communicated or balanced with proper alternatives, undermine trust in the platform and in the relationship with the very users who helped drive its progress.

@github Config based hooks is the one I'm watching. Onboarding new engineers to a repo with husky, lefthook, and a pile of pre commit scripts is always a half day tax. Native git config lets the setup live next to the code instead of in a README.

@github 操你妈野狗白皮猪订阅制天天改协议死全家了

@github Please fix the branch export for codespace I have exceeded my subscription I was closed out before I could commit

@github no more husky, yaaay.

@github such a good release

@github GitHub removed Opus 4.6 with its 3x premium request, leaving only Opus 4.7 with a 7.5x premium request. It seems users are being pushed to use the problematic GPT 5.4 model.