Highlights from Git 2.54

https://github.blog/open-source/git/highlights-from-git-2-54/

41•ingve•2d ago

Comments

samtrack2019•2d ago

the new git history command seems to be useful for quick reword, altho since i use lazygit/magit i don't really see much of a problem to me

olejorgenb•30m ago

Wish reword took a commit range though

ajoberstar•2d ago

Nice to see some seemingly jujutsu inspired features getting into Git core.

  git history reword ~= jj describe

  git history split ~= jj split

https://git-scm.com/docs/git-history

https://www.jj-vcs.dev/latest/cli-reference/#jj-describe

https://www.jj-vcs.dev/latest/cli-reference/#jj-split

aulin•54m ago

Not familiar with jj and don't want to get into bike shedding, but how is describe supposed to be a good name for history rewrites?

roblabla•29m ago

jj describe gives a name to a commit. In jj, everything rewrites the history, so there's no real point in calling it out in the command name since it's just the default behavior.

skydhash•25m ago

Not really familiar too, but jj has everything committed by default (no index, staging area, and uncommitted changes). You use ‘jj new’ to stop adding changes to the current commit.

‘jj describe’ lets you add a message to a commit as it’s not there by default.

auscompgeek•19m ago

describe is also the command you can use to edit the commit message of the change you're currently drafting. In jj there's no staging area, every modification to the working tree immediately gets integrated into the current commit. (This means if you have no diff in your working tree, you're actually on an empty commit.)

ufo•40m ago

I have always had this problem with hooks and new contributors: since hooks don't run by default if you just clone the repository, my open source projects get many PRs from new contributors that did not run the linting and commit hooks. I understand there's a security reason for this but what workflows have worked best for you to get everyone to run the hooks? And do you think the new config-based hooks can help new contributors?

sethops1•32m ago

> what workflows have worked best for you to get everyone to run the hooks

By running the linters and any other checks on CI instead.

baq•28m ago

autoformatter and autofix linter results can be committed and pushed by CI into the PR branch itself. this is a pain sometimes, but as a repo owner it should protect your sanity.

skydhash•20m ago

I just add a check workflow that test that the files are well formatted and linted. If it passes, one of the key things I check are changes to the configuration. Some tools allows for bypass comments, so I keep an eye out for those too.

IshKebab•7m ago

As well, not instead. Just add `pre-commit run -a` to your CI. Job done.

It's still annoying for new contributors though because they might not know how to set up pre-commit (which was quite a pain until recently because it's written in Python).

ufo•1m ago

We do run the linter on CI as well, but I think our comitters would get faster feedback if they ran the linter locally.

Surveillance vendors caught abusing access to telcos to track people's locations

I am building a cloud

Show HN: Honker – Postgres NOTIFY/LISTEN Semantics for SQLite

Alberta startup sells no-tech tractors for half price

Your hex editor should color-code bytes

Sneaky spam in conversational replies to blog posts

Jiga (YC W21) Is Hiring

Apple fixes bug that cops used to extract deleted chat messages from iPhones

Writing a C Compiler, in Zig

We found a stable Firefox identifier linking all your private Tor identities

5x5 Pixel font for tiny screens

Our newsroom AI policy

A True Life Hack: What Physical 'Life Force' Turns Biology's Wheels?

Isopods of the world

Arch Linux Now Has a Bit-for-Bit Reproducible Docker Image

The Onion to Take over InfoWars

Email could have been X.400 times better

Highlights from Git 2.54

Over-editing refers to a model modifying code beyond what is necessary

Website streamed live directly from a model

An amateur historian's favorite books about the Silk Road

Show HN: Built a daily game where you sort historical events chronologically

Technical, cognitive, and intent debt

Tempest vs. Tempest: The Making and Remaking of Atari's Iconic Video Game

Work with the Garage Door Up

Ping-pong robot beats top-level human players

Parallel agents in Zed

Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model

Books are not too expensive

Ultraviolet corona discharges on treetops during storms

Highlights from Git 2.54

Comments

Surveillance vendors caught abusing access to telcos to track people's locations

I am building a cloud

Show HN: Honker – Postgres NOTIFY/LISTEN Semantics for SQLite

Alberta startup sells no-tech tractors for half price

Your hex editor should color-code bytes

Sneaky spam in conversational replies to blog posts

Jiga (YC W21) Is Hiring

Apple fixes bug that cops used to extract deleted chat messages from iPhones

Writing a C Compiler, in Zig

We found a stable Firefox identifier linking all your private Tor identities

5x5 Pixel font for tiny screens

Our newsroom AI policy

A True Life Hack: What Physical 'Life Force' Turns Biology's Wheels?

Isopods of the world

Arch Linux Now Has a Bit-for-Bit Reproducible Docker Image

The Onion to Take over InfoWars

Email could have been X.400 times better

Highlights from Git 2.54

Over-editing refers to a model modifying code beyond what is necessary

Website streamed live directly from a model

An amateur historian's favorite books about the Silk Road

Show HN: Built a daily game where you sort historical events chronologically

Technical, cognitive, and intent debt

Tempest vs. Tempest: The Making and Remaking of Atari's Iconic Video Game

Work with the Garage Door Up

Ping-pong robot beats top-level human players

Parallel agents in Zed

Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model

Books are not too expensive

Ultraviolet corona discharges on treetops during storms