You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Any comment about upcoming Git Rev News edition 139 #860
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!
@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
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.
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.
@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, especially do you plan to add links related to those listed above? Except the one about git-hooks-ext which you have already added, the others don't seem to be part of this edition.
Please let me know in particular what you want to do about the related PRs, or just take a look at them and decide there.
There is also the YouTube link suggested by @To1neabove.
I find myself currently unable to push to GitHub (the
connection just hangs), but here is a patch fixing a typo
in the newly added text and a few more nits, in case someone
here were able and willing to apply (and push) it:
https://smrk.net/tmp/0001-rn-139-minor-copy-edit-part-2.patch
@mjaix Thank you for adding the git-hooks-ext, I hope it will help me to get some attention <3.
If you could reconsider adding the article explaining how it works, I would be really glad. I think it's a good read explaining reference-transactions to the public.
@mjaix Thank you for adding the git-hooks-ext, I hope it will help me to get some attention <3.
If you could reconsider adding the article explaining how it works, I would be really glad. I think it's a good read explaining reference-transactions to the public.
Activity
chriscool commentedon Sep 14, 2026
In this edition we might want to talk about the following:
ciembor commentedon Sep 18, 2026
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 commentedon Sep 18, 2026
ciembor commentedon Sep 18, 2026
@stepnem
Thanks, that's a fair concern.
The reason I chose
git-hooks-extis that I don't want the project to stay limited toreference-transaction. That's just the first mechanism I'm using to expose additional semantic events.Initially I only needed a
branch-createdhook. While looking into how to implement it, I realized thatreference-transactionprovides 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-extwould 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 commentedon Sep 21, 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 commentedon Sep 21, 2026
@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 commentedon Sep 21, 2026
We should actually take a look at:
To1ne commentedon Sep 24, 2026
I like smallish content creators making videos about Git. So I'd like to add this one https://youtu.be/KY4RDCpPHI0.
chriscool commentedon Sep 30, 2026
Draft email sent: https://lore.kernel.org/git/CAP8UFD1cA5uCpLRoozRMzemFwMbs9=ug+OQq3ATQcMA9HMK72A@mail.gmail.com/
sivaraam commentedon Sep 30, 2026
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 commentedon Sep 30, 2026
@sivaraam, thanks for the small but great articles about the upcoming Outreachy round, the previous GSoC round and the recent Git Merge!
To1ne commentedon Oct 1, 2026
@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 commentedon Oct 2, 2026
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.
2 remaining items
chriscool commentedon Oct 2, 2026
@jnareb, especially do you plan to add links related to those listed above? Except the one about
git-hooks-extwhich you have already added, the others don't seem to be part of this edition.Please let me know in particular what you want to do about the related PRs, or just take a look at them and decide there.
There is also the YouTube link suggested by @To1ne above.
jnareb commentedon Oct 2, 2026
I have a few more links I'd like to add, and I can then review links in this PR.
chriscool commentedon Oct 2, 2026
@jnareb, yes, please take a look at:
rn-139: Add "Your .gitconfig Is Missing These" video, suggested by @T…
jnareb commentedon Oct 2, 2026
I have added the rest of my links in 581ec2d
Added in d4a37b5
Added in 1e5d4ae
Already mentioned in previous editions of Git Rev News.
I have forgot about this.
Added in 002b539
Thanks @chriscool for the patience.
chriscool commentedon Oct 2, 2026
@jnareb, thanks for all the added links.
chriscool commentedon Oct 2, 2026
Edition published and announced in: https://lore.kernel.org/git/CAP8UFD0KAHvXvV-SqLd=sYohTvcgm2Dd52EfEY1XEbt3649Htg@mail.gmail.com/
@mjaix, you can still add fixes. Thanks.
stepnem commentedon Oct 2, 2026
ciembor commentedon Oct 2, 2026
@mjaix Thank you for adding the git-hooks-ext, I hope it will help me to get some attention <3.
If you could reconsider adding the article explaining how it works, I would be really glad. I think it's a good read explaining
reference-transactionsto the public.https://dev.to/ciembor/git-hooks-ext-the-missing-git-callbacks-for-reference-transactions-2l3l
mjaix commentedon Oct 2, 2026
jnareb commentedon Oct 2, 2026
Let's consider it for edition 140 (though I can also add it as sidenote to the existing link...).
mjaix commentedon Oct 2, 2026
mjaix commentedon Oct 2, 2026
chriscool commentedon Oct 3, 2026
Thanks @mjaix and @stepnem for the fixes!