Any comment about upcoming Git Rev News edition 139

[chriscool]

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-139.md

Feel free to comment in this issue, suggest topics, suggest persons to interview, or use the edit button (that looks like a pen) to edit and create a pull request with the changes you would like.

Let's try to publish this edition around the end of September 2026!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster @stepnem

[chriscool]

In this edition we might want to talk about the following:

• Git Merge 2026
• end of GSoC 2026 with all the contributors passing the final evaluation
• Git participating in Outreachy December 2026 cohort

[ciembor]

Maybe this will interest you: https://github.com/ciembor/git-hooks-ext

I'm looking for feedback and hoping to get some attention from the Git community.

[stepnem]

Maybe this will interest you: https://github.com/ciembor/git-hooks-ext I'm looking for feedback and hoping to get some attention from the Git community.

@ciembor thank you for sharing, this looks useful (in theory; I have never had a use for the reference-transaction hook myself so far). My main feedback, having looked at the README and a bit of the documentation, is that I would suggest changing the project/tool name to something more fitting like "git-reference-transaction-hook-ext": 1. "git-hooks-ext" makes it sound like something much more general than it appears to be (i.e., only extending one of the many built-in git hooks) 2. a longer, more descriptive name brings little inconvenience here as the direct interaction with the command seems limited (installation, events listing) 3. the project repo is 4 hours old, so any renaming churn caused should be minimal

[ciembor]

@stepnem

Thanks, that's a fair concern.

The reason I chose git-hooks-ext is that I don't want the project to stay limited to reference-transaction. That's just the first mechanism I'm using to expose additional semantic events.

Initially I only needed a branch-created hook. While looking into how to implement it, I realized that reference-transaction provides enough information to derive many more useful events, so the first version ended up exposing 19 semantic events for branches, remote branches, tags, stashes, and notes.

The longer-term goal is to keep extending this idea using other existing Git hooks and mechanisms as well. For example, events around commits, amend, rebase, merge, checkout/branch switching, detached HEAD, received pushes, and other operations where Git exposes enough reliable information.

So while git-reference-transaction-hook-ext would describe the current implementation more precisely, I think it would also make the project name too narrow for where I want to take it. The goal is essentially to provide as many useful missing semantic Git hook events as can be implemented reliably.

That said, I agree the README should make this broader scope much clearer.

[To1ne]

In this edition we might want to talk about the following:

• Git Merge 2026

@chriscool Yes, I agree. For the technical portion of this edition I think it would be a good idea to have a summary on the topics discussed at the contributor summit. Would be great for the wider community to get some insight in things what the maintainers are thinking about.

I'm happy to help writing that summary.

[chriscool]

@To1ne, I agree it would be great. Thank you for volunteering to help with that! If you can write a draft, I will be happy to contribute to it.

[chriscool]

We should actually take a look at:

• rn-139: add WebTerm Learn to Git tools and sites #867
• Update edition-139.md - git-hooks-ext #866
• Rev News edition 138: add crux to Other News #858
• rn-137: Add learngit.io updates to tools & sites #855

[To1ne]

I like smallish content creators making videos about Git. So I'd like to add this one https://youtu.be/KY4RDCpPHI0.

[chriscool]

Draft email sent: https://lore.kernel.org/git/CAP8UFD1cA5uCpLRoozRMzemFwMbs9=ug+OQq3ATQcMA9HMK72A@mail.gmail.com/

[sivaraam]

I included the Git Merge participation and pushed as 2672f04 amd 59c1f59 (excuse the redudant commit).

I raised the following PR to include the GSoC and Outreachy details: #870 (thanks @chriscool for merging it!)

[chriscool]

@sivaraam, thanks for the small but great articles about the upcoming Outreachy round, the previous GSoC round and the recent Git Merge!

[To1ne]

@sivaraam My apologies I wasn't able to write a summary about the Git Contributor Summit, I simply totally forgot about it. But I agree with what you've written in the draft right now.

[jnareb]

I'm a bit late - first part of my links have landed in 6db86ff and 5796142 , I'll try to add the rest of them soon.