Skip to content

Commit 4ba8d72

Browse files
committed
rn-128: Add links to news, articles, videos, tools, and sites
1 parent d4ffacf commit 4ba8d72

File tree

1 file changed

+178
-2
lines changed

1 file changed

+178
-2
lines changed

rev_news/drafts/edition-128.md

Lines changed: 178 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,15 +138,191 @@ This edition covers what happened during the months of September and October 202
138138

139139
__Various__
140140

141+
+ [Git considers SHA-256, Rust, LLMs, and more](https://lwn.net/Articles/1042172/)
142+
by Jonathan Corbet on LWN\.net.
143+
+ [Git Developers Talk About Potentially Releasing Git 3.0 By The End Of Next Year](https://www.phoronix.com/news/Git-3.0-Release-Talk-2026)
144+
by Michael Larabel on Phoronix.
145+
+ [GitHub is migrating to Azure! And goodbye to new development for a year.](https://www.redhotcyber.com/en/post/github-is-migrating-to-azure-and-goodbye-to-new-development-for-a-year/)
146+
by Redazione RHC on Red Hot Cyber.
147+
+ [Fedora Moves Towards Forgejo](https://fedoramagazine.org/fedora-moves-towards-forgejo-a-unified-decision/)
148+
by Matthew Miller and Akashdeep Dhar on December 4, 2024
149+
in Fedora Magazine.
150+
+ [Forgejo](https://forgejo.org/) is a self-hosted lightweight software forge,
151+
written in Go; nowadays a hard fork of Gitea (which in turn was based on Gogs).
152+
It was first mentioned in passing in [Git Rev News Edition #103](https://git.github.io/rev_news/2023/09/30/edition-103/).
153+
141154

142155
__Light reading__
143156

144-
<!---
157+
+ [building for the future: on tangled's existence and direction](https://anirudh.fi/future)
158+
by Anirudh Oppiliappan on their blog;
159+
also published [at icy takes blog](https://icy.leaflet.pub/3m47cll72hs25) on ATProto.
160+
+ [Tangled.sh](https://blog.tangled.sh/intro) is a new social-enabled Git collaboration platform
161+
built on top of the AT Protocol / ATProto
162+
(which is behind [BlueSky](https://bsky.app/) microblogging federated social media service).
163+
It was first mentioned in [Git Rev News Edition #125](https://git.github.io/rev_news/2025/07/31/edition-125/).
164+
+ [6 months of Tangled: a quick recap, and notes on the future](https://blog.tangled.org/6-months)
165+
by by Anirudh Oppiliappan and Akshay Oppiliappan on Tangled Blog.
166+
+ [Socially self-hosting source code with Tangled on Bluesky](https://anil.recoil.org/notes/disentangling-git-with-bluesky)
167+
by Anil Madhavapeddy, Professor of Planetary Computing on his blog.
168+
+ [Redistributing Git with Nostr](https://fiatjaf.com/18ff5416.html)
169+
by início on their blog.
170+
+ There exists [gitstr (`git str`)](https://github.com/fiatjaf/gitstr),
171+
which is a tool to send and receive Git patches
172+
over [Nostr](https://nostr.com/), using [NIP-34](https://github.com/nostr-protocol/nips/pull/997)
173+
(first mentioned in [Git Rev News Edition #109](https://git.github.io/rev_news/2024/03/31/edition-109/)).
174+
+ Note that the [git-credential-oauth](https://github.com/hickford/git-credential-oauth),
175+
a Git credential helper that securely authenticates to GitHub, GitLab, BitBucket and Gerrit
176+
using [OAuth](https://datatracker.ietf.org/wg/oauth/about/),
177+
can replace the "create an account; pick a password; confirm an email address; setup SSH keys for pushing" step.
178+
+ [How GitHub won software development](https://www.infoworld.com/article/4069045/how-github-won-software-development.html)
179+
by Nick Hodges on Rubber Duck Reflections opinions blog on InfoWorld.
180+
+ [You already have a git server](https://maurycyz.com/misc/easy_git/)
181+
on Maurycy's blog;
182+
describes how one can serve Git repositories via SSH (with SSH access)
183+
or via dumb HTTP (with a web server).
184+
+ [Simple automated deployments using git push](https://garrido.io/notes/simple-automated-deployments-git-push/)
185+
by Gabriel Garrido on his blogs / notes (2024).
186+
+ [Discussion of the Benefits and Drawbacks of the Git Pre-Commit Hook](https://yeldirium.de/2025/10/09/pre-commit-hooks/index.html)
187+
by Hannes Leutloff on his blog.
188+
+ [You can use `fzf` to review git commits](https://jvns.ca/til/fzf-preview-git-commits/)
189+
by Julia Evans in her TIL (Today I've Learned) section.
190+
+ See also [Improving shell workflows with fzf](https://seb.jambor.dev/posts/improving-shell-workflows-with-fzf/),
191+
mentioned in [Git Rev News Edition #74](https://git.github.io/rev_news/2021/04/30/edition-74/), and
192+
[Curing A Case Of Git-UX](https://oppi.li/posts/curing_a_case_of_git-UX/),
193+
mentioned in [Git Rev News Edition #126](https://git.github.io/rev_news/2025/08/31/edition-126/).
194+
+ [Switch to Jujutsu already: a tutorial](https://www.stavros.io/posts/switch-to-jujutsu-already-a-tutorial/)
195+
by Stavros on Stavros' Stuff.
196+
+ [Jujutsu (`jj`)](https://jj-vcs.github.io/jj/) is a Git-compatible version control system
197+
written in Rust, which was first mentioned in
198+
[Git Rev News Edition #85](https://git.github.io/rev_news/2022/03/31/edition-85/).
199+
+ [Magit Is Amazing!](https://heiwiper.com/posts/magit-is-awesome/)
200+
by Abdallah Maouche (heiwiper) on his blog
201+
(how it does things that others need to use Jujutsu over Git for).
202+
+ [Magit](https://magit.vc/) is a popular [Emacs](https://www.gnu.org/software/emacs) editor interface to Git,
203+
first mentioned (in passing) in [Git Rev News Edition #6](https://git.github.io/rev_news/2015/08/05/edition-6/).
204+
+ [Branching in a Sapling Monorepo](https://engineering.fb.com/2025/10/16/developer-tools/branching-in-a-sapling-monorepo/)
205+
+ [Sapling](https://sapling-scm.com/) is a scalable, user-friendly, and open-source source control system
206+
that powers Meta's (Facebook's) monorepo.
207+
It was first mentioned in [Git Rev News Edition #93](https://git.github.io/rev_news/2022/11/30/edition-93/).
208+
+ [Stop Rebasing Everything: Your Git History Isn’t That Special](https://dev.to/dolig/stop-rebasing-everything-your-git-history-isnt-that-special-ln3),
209+
an argument in the merge-vs-rebase debate.
210+
by Guillaume on DEV\.to.
211+
+ [Diff Algorithms](https://flo.znkr.io/diff/)
212+
by Florian Zenker on Florian Zenker's website.<br>
213+
The result of this exploration was [znkr.io/diff](https://znkr.io/diff),
214+
a difference algorithm module for Go.
215+
+ Note that with [`git diff`](https://git-scm.com/docs/git-diff)
216+
you can choose between `myers` (default), `minimal`, `patience` and `histogram` algorithms.
217+
+ [Git Super-Power: The Three-Way Merge](https://qsantos.fr/2024/05/01/git-super-power-the-three-way-merge/)
218+
by Quentin Santos on his blog (2024).<br>
219+
Provides the following tl;dr: `git config --global merge.conflictstyle diff3`.
220+
+ [Anyone Can Commit Code as You on GitHub (Here's How to Stop Them)](https://www.nickyt.co/blog/anyone-can-commit-code-as-you-on-github-heres-how-to-stop-them-2in7/)
221+
with signed commits (with tutorial focusing on macOS using GPG Keychain).
222+
Written by Nick Taylor on his Just Some Dev blog.
223+
+ [GitHub Ensloppification](https://dbushell.com/2025/08/11/github-ensloppification/)
224+
by David Bushell on his blog.
225+
+ ["GitHub" Is Starting to Feel Like Legacy Software](https://www.mistys-internet.website/blog/blog/2024/07/12/github-is-starting-to-feel-like-legacy-software/)
226+
rant by Misty De Méo on her blog (2024).
227+
+ [Implementing Conventional Commits with Jira Ticket Prefix Validation](https://heristop.github.io/blog/2024-07-09-conventional-commit-jira/)
228+
by Alexandre Mogère (heristop) on Zazen Code.
229+
+ The [Conventional Commits](https://www.conventionalcommits.org/) specification
230+
was first mentioned in [Git Rev News Edition #52](https://git.github.io/rev_news/2019/06/28/edition-52/),
231+
and in many editions since.
232+
+ [Conventional Commits considered harmful](https://larr.net/p/cc.html)
233+
(or rather overly strict enforcement of the standard),
234+
rant by Salih Muhammed, with a few further links.
235+
+ [Contribute to GitFichas](https://jtemporal.com/contribute-to-gitfichas/)
236+
by Jessica Temporal on her blog.
237+
+ [GitFichas](https://gitfichas.com/en) (also know as GitStudyCards)
238+
is a collection of study cards about Git,
239+
for devs that might need a refresher about Git commands.
240+
Mentioned in [the previous edition of Git Rev News](https://git.github.io/rev_news/2025/09/30/edition-127/).
241+
242+
145243
__Easy watching__
146-
-->
244+
245+
+ [Jujutsu at Google](https://www.youtube.com/watch?v=v9Ob5yPpC0A&list=PLOU2XLYxmsILM5cRwAK6yKdtKnCK6Y4Oh&index=8)
246+
([slides](https://drive.google.com/file/d/1dVzug1lHoOxdbFu8gcCJCu-G_uVMUATI/edit))
247+
on Google for Developers channel on YouTube;
248+
part of [JJ Con 2025 playlist](https://www.youtube.com/playlist?list=PLOU2XLYxmsILM5cRwAK6yKdtKnCK6Y4Oh).<br>
249+
In this talk from Martin von Zweigbergk presents
250+
on Jujutsu architecture and future plans.<br>
251+
JJ Con 2025 was a dedicated conference hosted by Google
252+
for the [Jujutsu](https://jj-vcs.github.io/jj/latest/) version control system.
253+
+ [Solving Git's Pain Points with Jujutsu (with Martin von Zweigbergk)](https://www.youtube.com/watch?v=ulJ_Pw8qqsE)
254+
on Developer Voices channel on YouTube.
255+
256+
257+
__Scientific papers__
258+
259+
+ Ya-Nan Li, Yaqing Song, Qiang Tang, Moti Yung:
260+
_"End-to-End Encrypted Git Services"_,
261+
Cryptology {ePrint} Archive, Paper 2025/1208,
262+
<https://eprint.iacr.org/2025/1208>,
263+
DOI:10.1145/3719027.3744815
264+
+ See _"Scientists develop end-to-end encryption for git services"_
265+
article by University of Sydney, edited by Stephanie Baum, reviewed by Robert Egan,
266+
on TechXplore.
267+
+ S.R.P. van Hal, M. Post, K. Wendel:
268+
_"Generating Commit Messages from Git Diffs"_,
269+
[arXiv:1911.11690](https://arxiv.org/abs/1911.11690) (2019)<br>
270+
mentions "inherent shortcoming of current commit message generation models,
271+
which perform well by memorizing certain constructs."
272+
147273

148274
__Git tools and sites__
149275

276+
+ [diff-modulo-base](https://git.sr.ht/~nhaehnle/diff-modulo-base)
277+
is a tool that allows you to compare the relevant changes
278+
of two versions of a rebased branch given three input diffs:
279+
two _base_ diffs that show the changes since the respective merge bases
280+
and a _target_ diff between the branches you are actually interested in.
281+
282+
It is very similar to (and actually builds on) `git range-diff`,
283+
but differs in resulting output.
284+
Written in Rust, under MIT License.
285+
+ [Worktree Manager](https://github.com/jarredkenny/worktree-manager) (wtm)
286+
is s fast, modern CLI tool for managing Git worktrees in bare repositories.
287+
Written in TypeScript for Bun, under MIT License.
288+
+ [git-metrics](https://github.com/jdrouet/git-metrics)
289+
is a Git extension that makes it possible to track metrics about your project,
290+
which are stored within the git repository (using `git notes`).
291+
Written in Rust, under MIT License.<br>
292+
Described in [Build metrics and budgets with git-metrics](https://dev.to/jdrouet/build-metrics-and-budgets-with-git-metrics-4pb4)
293+
article by Jérémie Drouet on DEV\.to (2024).
294+
+ There is another [git-metrics](https://github.com/Praqma/git-metrics) tool,
295+
by Praqma / Eficode DevOps company,
296+
which consists of a set of scripts to analyse a Git repository for metrics
297+
such as lead time and open branches. Writen in Python, no license provided.
298+
It was mentioned in passing in [Git Rev News Edition #48](https://git.github.io/rev_news/2019/02/27/edition-48/).
299+
+ [git-spice](https://abhinav.github.io/git-spice/) is a tool for stacking Git branches.
300+
It lets you manage and navigate stacks of branches, conveniently modify and rebase them,
301+
and create GitHub Pull Requests or GitLab Merge Requests from them.
302+
Written in Go, under GPL 3.0 License.
303+
+ A _stacked branch_ refers to a set of branches that build upon each other in a linear sequence.
304+
Stacked branches or stacked diffs were first mentioned in [Git Rev News #44](https://git.github.io/rev_news/2018/10/24/edition-44/),
305+
and most recently in [Git Rev News #127](https://git.github.io/rev_news/2025/09/30/edition-127/),
306+
where you can find even more links about this technique.
307+
+ [Git Granary](https://git.dbushell.com/dbushell/granary)
308+
is a [Git Large File Storage](https://git-lfs.com/) (LFS)
309+
server implementation written in TypeScript. Under MIT License.
310+
Git Granary was designed for self-hosted personal use.<br>
311+
See [Git Granary](https://dbushell.com/2024/07/25/git-granary/)
312+
blog post by David Bushell on his blog (2024).
313+
+ [gibr](https://github.com/ytreister/gibr) is a Git CLI tool
314+
for intelligently creating branch names.
315+
It connects your Git workflow to your issue tracker for that purpose;
316+
currently supporting GitHub, GitLab, Jira, and Linear
317+
(with Monday\.com support planned).
318+
Written in Python, under MIT License.
319+
+ [0github.com](https://0github.com/)
320+
is a service offering a heatmap diff viewer for code reviews,
321+
color-coding every diff line/token by how much human attention it probably needs.
322+
To try it, replace github.com with 0github.com in any GitHub pull request url.
323+
The [cmux](https://cmux.dev/) engine it uses is open source (MIT License).
324+
It uses LLM (Large Language Model) to perform this task.
325+
150326

151327
## Releases
152328

0 commit comments

Comments
 (0)