rn-129: Add links to news, articles, videos, tools, and services

jnareb · jnareb · commit 26d969abf6bf · 2025-12-01T01:00:36.000+01:00
diff --git a/rev_news/drafts/edition-129.md b/rev_news/drafts/edition-129.md
@@ -81,15 +81,275 @@ This edition covers what happened during the months of October and November 2025
 
 __Various__
 
+- [What’s new in Git 2.52.0?](https://about.gitlab.com/blog/whats-new-in-git-2-52-0/)
+  by Christian Couder, Patrick Steinhardt, Toon Claes on GitLab Blog.
+  Highlights include `git last-modified` command,
+  `git fast-export` and `git fast-import` signature-related improvements,
+  new and improved `git maintenance` strategies,
+  new subcommand for new `git repo` to display repository metrics, etc.
+- [Highlights from Git 2.52](https://github.blog/open-source/git/highlights-from-git-2-52/)
+  by Taylor Blau on GitHub Blog.
+  Mentions  `git last-modified` command for tree-level blame information,
+  advanced repository maintenance strategies for `git maintenance`,
+  new sub-commands be added to `git refs`, new `git repo` command, etc.
+- [lakeFS Acquires DVC, Uniting Data Version Control Pioneers to Accelerate AI-ready Data](https://lakefs.io/media-mentions/lakefs-acquires-dvc-uniting-data-version-control-pioneers/)
+  announcement by LakeFS on their Mentions Media page
+    - [DVC Joins lakeFS: Your Questions Answered!](https://dvc.org/blog/dvc-joins-lakefs-your-questions-answered/)
+      by Jeny De Figueiredo on DVC Blog.
+    - [A Shared Vision for the Future of DVC](https://dvc.org/blog/a-shared-vision-for-the-future-of-dvc/)
+      by Dmitry Petrov on DVC Blog.
+	- See also [“Data Management” section of Awesome MLOps](https://github.com/kelvins/awesome-mlops#data-management),
+	  mentioned in [Git Rev News Edition #116](https://git.github.io/rev_news/2024/10/31/edition-116/),
+	  in which edition you can also find references to DVC and lakeFS,
+	  and other similar tools (though the list there is missing
+	  [Meltano](https://meltano.com/) (first mentioned in [Git Rev News Edition #42](https://git.github.io/rev_news/2018/08/22/edition-42/)) and
+	  [Pachyderm](https://www.pachyderm.com/) (first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/)).
+- [20 Years of Git, 2 days at GitHub HQ: Git Merge 2025 highlights 🎉](https://github.blog/open-source/git/20-years-of-git-2-days-at-github-hq-git-merge-2025-highlights/)
+  by Lee Reilly on GitHub Blog.
+  See also [the previous edition of Git Rev News](https://git.github.io/rev_news/2025/10/31/edition-128/)
+  for more links.
+
 
 __Light reading__
+
 - [Version Control in the Age of AI: The Complete Guide](https://www.git-tower.com/blog/version-control-in-the-age-of-ai)
-<!---
+  by Bruno Brito on Git Tower blog.
+- [Analyzing 10 years of accepted patch series to Git](https://benknoble.github.io/blog/2025/11/14/git-patch-series-length/)
+  by D. Ben Knoble on his Junk Drawer personal blog.
+- [Mergiraf: syntax-aware merging for Git](https://lwn.net/Articles/1042355/)
+  by Daroc Alden on LWN\.net.
+    - [Mergiraf](https://mergiraf.org/introduction.html) is a merge-conflict resolver
+      that uses a generic algorithm plus a small amount of language-specific knowledge
+      to solve conflicts that Git's default strategy cannot.
+      It was mentioned in [Git Rev News Edition #117](https://git.github.io/rev_news/2024/11/30/edition-117/).
+	- The Mergiraf author recommends using the tool together with
+	  [Difftastic](https://difftastic.wilfred.me.uk/), a structural diff tool
+	  that understands syntax, mentioned in [Git Rev News Edition #86](https://git.github.io/rev_news/2022/04/30/edition-86/).
+- [Should I Switch From Git to Jujutsu](https://etodd.io/2025/10/02/should-i-switch-from-git-to-jujutsu/)
+  by Evan Todd on his personal blog.
+    - [Jujutsu (`jj`)](https://jj-vcs.github.io/) is a Git-compatible
+	  version control system written in Rust, which was first mentioned
+	  in [Git Rev News Edition #85](https://git.github.io/rev_news/2022/03/31/edition-85/).
+	- See also [Switch to Jujutsu already: a tutorial](https://www.stavros.io/posts/switch-to-jujutsu-already-a-tutorial/)
+	  by Stavros on Stavros’ Stuff,
+	  mentioned in [the previous edition](https://git.github.io/rev_news/2025/10/31/edition-128/)
+- [Why Git is the first tool every new developer needs to learn](https://www.howtogeek.com/beginning-git-what-it-is-and-why-its-crucial/)
+  by Graeme Peacock on How-To Geek.
+- [Git for Vibe Coders](https://www.kdnuggets.com/git-for-vibe-coders),
+  just enough to stop Claude from accidently deleting your code and database.
+  By Abid Ali Awan on KDnuggets.
+- [4 advanced git commands you probably haven't heard of](https://www.howtogeek.com/advanced-git-commands-you-probably-havent-heard-of/):
+  [`git clean`](https://git-scm.com/docs/git-clean),
+  [`git bisect`](https://git-scm.com/docs/git-bisect),
+  [`git cherry-pick`](https://git-scm.com/docs/git-cherry-pick),
+  [`git revert`](https://git-scm.com/docs/git-revert),
+  by Bobby Jack on How-To Geek.
+- [Setting File Permissions in Git](https://www.tvaidyan.com/2025/11/13/setting-file-permissions-in-git/)
+  by Tom Vaidyan on his personal blog;
+  though I wonder why he shows low-level `git update-index --chmod=+x <file>` ("plumbing")
+  first, instead of user-facing `git add --chmod=+x <file>` ("porcelain" command).
+- [Why You Should Be Using Git Worktrees](https://blog.randombits.host/why-you-should-be-using-git-worktrees/)
+  by Conor in Quick Tip on their Random Bits personal blog
+  (it includes their helper `gwc`, i.e. git worktree create, shell script).
+- [tree-me: Because git worktrees shouldn't be a chore](https://haacked.com/archive/2025/11/21/tree-me/)
+  by Phil Haack on his You've Been Haacked blog.
+- [Use skip-worktree to ignore modified files](https://www.brandonpugh.com/til/git/skip-worktree-ignore-modified-files/)
+  by Brandon Pugh in "TIL: Today I learned..." section on his blog.
+- [Managing Multiple Projects in One Repository: Submodules, Subtrees, Monorepos & Partial Cloning Explained](https://dev.to/k-kibet/managing-multiple-projects-in-one-repository-submodules-subtrees-monorepos-partial-cloning-21mc)
+  by Kibet Korir (K-kibet) for Codespear on DEV\.to.
+- [Automatically switching Git Identities and SSH Keys on the same machine](https://dev.to/enbis/automatically-switching-git-identities-and-ssh-keys-on-the-same-machine-75n)
+  with the help of `includeIf` directive in the `.gitconfig` file,
+  by Enrico Bison (enbis) on DEV\.to.  See also:
+    - [Splitting SSH and git configs](https://iamjonfry.com/splitting-ssh-and-git-configs/)
+	  mentioned in [Git Rev News Edition #42](https://git.github.io/rev_news/2018/08/22/edition-42/).
+	- [How to Use Multiple Git Configs on One Computer](https://www.freecodecamp.org/news/how-to-handle-multiple-git-configurations-in-one-machine/)
+	  mentioned in [Git Rev News Edition #71](https://git.github.io/rev_news/2021/01/28/edition-71/).
+	- [How I configure my Git identities](https://www.benji.dog/articles/git-config/)
+	  mentioned in [Git Rev News Edition #117](https://git.github.io/rev_news/2024/11/30/edition-117/).
+	- [One PC, Multiple Git Configs (This Will Save You Time!)](https://medium.com/@matteopampana/one-pc-multiple-git-configs-this-will-save-you-time-f702880744f7)
+	  mentioned in [Git Rev News Edition #120](https://git.github.io/rev_news/2025/02/28/edition-120/).
+- [Git: Amend any commit](https://ylan.segal-family.com/blog/2025/11/15/git-ammend-any-commit/)
+  (scripting around `git commit --amend`, and `git commit --fixup` + `git rebase --autosquash`)
+  by Ylan Segal on his "on.code && such" blog.
+- [If You Think YOUR Commit Messages Are Bad, Just Wait...](https://dev.to/sylwia-lask/if-you-think-your-commit-messages-are-bad-just-wait-3fgk)
+  by Sylwia Laskowska on DEV\.to,
+  with others providing more examples in comments.
+- [Mistakes I see engineers making in their code reviews](https://www.seangoedecke.com/good-code-reviews/)
+  by Sean Goedecke on his blog.
+- [Testable Dotfiles Management With Chezmoi](https://shunk031.me/post/testable-dotfiles-management-with-chezmoi/)
+  by Shunsuke Kitada (北田 俊輔), Ph.D. on shunk031\.me.
+- [Backing up my repositories to self-hosted Gitea](https://blog.kulman.sk/self-hosted-gitea-backup/)
+  by Igor Kulman on his personal blog.
+   - [Gitea](https://about.gitea.com/) is a Go-based software forge,
+     a fork of [Gogs](https://gogs.io/).
+	 It was first mentioned in [Git Rev News Edition #23](https://git.github.io/rev_news/2017/01/25/edition-23/).
+- [Fixing Vercel's 'Git Author Must Have Access' Error](https://www.pavlinbg.com/posts/fix-vercel-git-author-error),
+  which was caused by the way how Vercel handles multiple accounts.
+  Written by Pavlin Gunov (PavlinBG) on his blog.
+- [Running DVC on a SLURM cluster](https://dvc.org/blog/dvc-slurm-cluster-exscientia/)
+  by Dom Miketa on DVC Blog (2024).
+    - [DVC](https://dvc.org/) (Data Version Control),
+      an open-source version control system for data science projects,
+	  was first mentioned in [Git Rev News Edition #23](https://git.github.io/rev_news/2017/01/25/edition-23/).
+
+
 __Easy watching__
--->
+
+- [How to ensure the Git community is / stays healthy: Emily Shaffer / Patrick Steinhardt & guests](https://www.youtube.com/watch?v=vKsOFHNSb4Q)
+  on GitButler on YouTube [44:42].
+
 
 __Git tools and sites__
 
+- [gitlogue](https://github.com/unhappychoice/gitlogue)
+  is a cinematic Git commit replay tool for the terminal,
+  turning your Git history into a living, animated story;
+  with realistic typing animations, syntax highlighting, and file tree transitions,
+  transforming code changes into a visual experience.
+  Written mainly in Rust, under ISC License.
+- [PyDriller](https://github.com/ishepard/pydriller) is a Python framework
+  that helps developers in analyzing Git repositories.
+  With PyDriller you can easily extract information about
+  commits, developers, modified files, diffs, and source code.
+  Written in Python, under Apache 2.0 license.
+- [tree-me](https://github.com/haacked/dotfiles/blob/main/bin/tree-me)
+  is a minimal git worktree helper
+  that leverages git's native capabilities.
+  It uses git-like subcommands and follows conventions so you don’t have to think:
+  auto-detects repository name from your git remote,
+  auto-detects default branch, organizes by repo, provides tab completion, etc.
+  Single bash script, part of [haacked dotfiles](https://github.com/haacked/dotfiles).
+  No license.
+    - See also [Worktree Manager](https://github.com/jarredkenny/worktree-manager) (wtm),
+	  a fast, modern CLI tool for managing Git worktrees in bare repositories,
+	  mentioned in [Git Rev News Edition #128](https://git.github.io/rev_news/2025/10/31/edition-128/).
+- [Spelungit](https://github.com/haacked/spelungit) is a Model Context Protocol (MCP) server
+  for exploring Git commit history using semantic search.
+  With this tool you can search through commits with natural language commands
+  like "Search git history to find out why was this class added?",
+  or "search_commits(query="authentication login changes", limit=5)".
+  Uses Microsoft's all-MiniLM-L6-v2 embeding model via [sentence-transformers](https://www.sbert.net/),
+  or deterministic hash-based embeddings when sentence-transformers is unavailable.
+  Written in Python (with a few Bash scripts), under MIT License.
+    - See also [Spelungit: When `git log --grep` isn't enough](https://haacked.com/archive/2025/09/29/announcing-spelungit/)
+	  by Phil Haack on You've Been Haacked blog.
+- [forgit](https://github.com/wfxr/forgit) is a utility tool
+  powered by [fzf](https://github.com/junegunn/fzf) (command-line fuzzy finder)
+  for using Git interactively.
+  Written in shell, under MIT license.
+- [gitnr](https://github.com/reemus-dev/gitnr) is a cross-platform CLI utility
+  to create `.gitignore` files using one or more templates
+  from [TopTal](https://github.com/toptal/gitignore) (<https://gitignore.io>),
+  [GitHub](https://github.com/github/gitignore), or your own collection.
+  Written in Rust, under MIT License.
+- [`mani`](https://manicli.com/) is a CLI tool
+  that helps you manage multiple repositories.
+  It's useful when you are working with microservices, multi-project systems,
+  multiple libraries, or just a collection of repositories
+  and want a central place for pulling all repositories and running commands across them.
+  Written in Go, under MIT License.
+- [eget](https://github.com/zyedidia/eget) is a command-line tool
+  for easily fetching and extracting pre-built binaries from GitHub releases.
+  Written in Go, under MIT License.
+- [dunk](https://github.com/darrenburns/dunk) is a tool
+  to provide prettier git diffs in the terminal
+  by pipe-ing `git diff` output into it (`git diff | dunk` or `git diff | dunk | less -R`).
+  In is very early stages of development.
+  Written in Python, under MIT License.
+    - See also [git-delta](https://dandavison.github.io/delta/),
+	  a syntax-highlighting pager for git, diff, grep, and blame output.
+	  It was first mentioned in [Git Rev News Edition #86](https://git.github.io/rev_news/2022/04/30/edition-86/),
+	  though there is another [delta](https://github.com/octavore/delta)
+	  command-line diff tool which was first mentioned in [edition #9](https://git.github.io/rev_news/2015/11/11/edition-9/).
+	- See also [diff-so-fancy](https://github.com/so-fancy/diff-so-fancy) tool,
+	  which beside piping `git diff` output to it,
+	  can also be used as `core.pager` and `interactive.diffFilter`.
+	  It was first mentioned in [Git Rev News Edition #13](https://git.github.io/rev_news/2016/03/16/edition-13/).
+	- There is also [`contrib/diff-highlight`](https://github.com/git/git/tree/master/contrib/diff-highlight)
+	  diff pager script in the Git repository, written in Perl.
+	  It was mentioned in [Git Rev News Edition #53](https://git.github.io/rev_news/2019/07/24/edition-53/).
+- [GitType](https://github.com/unhappychoice/gittype) is a CLI tool
+  that turns your own source code into typing challenges.
+  Because why practice with boring [lorem ipsum](https://www.lipsum.com/)
+  when you can type your beautiful `fn main()` implementations?
+  Written in Rust, under MIT License.
+- [Serie](https://github.com/lusingander/serie) is a TUI tool that
+  provides rich git commit graph in your terminal.
+  Written in Rust, under MIT License.
+    - See also [tig](https://jonas.github.io/tig/),
+	  an ncurses-based text-mode interface for Git,
+	  first mentioned in [Git Rev News Edition #18](https://git.github.io/rev_news/2016/08/17/edition-18/).
+- [prettydiff](https://github.com/prettydiff/prettydiff) is a beautifier and language aware
+  code comparison tool for many languages. It also minifies and a few other things.
+  There is web service showing how the tool works at <https://prettydiff.com/tool.xhtml>.
+  Written in TypeScript and HTML,
+  under [CC0](https://creativecommons.org/public-domain/cc0/) license.
+- [fnox: Fort Knox for your secrets](https://fnox.jdx.dev/)
+  is a tool to manage secrets with encryption, or cloud providers, or both.
+  Fnox uses a simple TOML config file (`fnox.toml`) that you check into Git;
+  secrets are either encrypted inline, or provided as references
+  that points to a secret in age, AWS, 1Password, etc.
+  Written in Rust, under MIT License.
+- [asdf](https://asdf-vm.com/guide/introduction.html) is a tool version manager.
+  All tool version definitions are contained within one file (`.tool-versions`)
+  which you can check in to your project's Git repository to share with your team,
+  ensuring everyone is using the exact same versions of tools.
+  Written mainly in Bash and Go, under MIT License.
+- [grebedoc.dev](https://grebedoc.dev/) is a service
+  that offers static site hosting for Git forges;
+  it publishes the `pages` branch in your Git repository as a website on your domain.
+  More specifically, it is a public deployment of
+  [git-pages](https://codeberg.org/git-pages/git-pages)
+  and [Caddy](https://caddyserver.com/), configured to work especially with
+  [Codeberg](https://codeberg.org/) but also with other Git forges.
+  It is operated by Catherine 'whitequark' and teammates.
+    - Compare with [GitHub Pages](https://docs.github.com/en/pages),
+	  [GitLab Pages](https://docs.gitlab.com/user/project/pages/),
+	  [static websites on Bitbucket Cloud](https://support.atlassian.com/bitbucket-cloud/docs/publishing-a-website-on-bitbucket-cloud/),
+	  [Codeberg Pages](https://codeberg.page/) (can't guarantee high availability),
+	  [sourcehut pages](https://srht.site/), and
+	  [Cloudflare Pages](https://pages.cloudflare.com/) (JAMstack platform), etc.
+- [gitsuggest](https://github.com/csurfer/gitsuggest) is a tool
+  to suggest GitHub repositories based on the repositories you have shown interest in
+  by “starring”. It is using Latent Dirichlet Allocation (LDA) method.
+  There is also [gitSuggest](http://www.gitsuggest.com/) service (in beta), on Heroku.
+  Written on Python, under MIT License.
+- [Josh](Just One Single History) ([repo](https://github.com/josh-project/josh))
+  is a tool that combines the advantages of monorepos with those of multirepos
+  by leveraging a blazingly-fast, incremental, and reversible implementation
+  of git history filtering.
+  Note that to guarantee filters are reversible
+  Josh restricts the kind of filter that can be used.
+  Use cases include partial cloning, workspaces, simplified CI/CD;
+  this tool also provides GraphQL API.
+  Josh is distributed via [Docker Hub](https://hub.docker.com/r/joshproject/josh-proxy),
+  and you can start it with appropriate `docker run` command.
+  See its [Frequently Asked Questions](https://josh-project.github.io/josh/faq.html#frequently-asked-questions)
+  for comparison with `git sparse-checkout`, partial clone, submodules, `git subtree`,
+  and `git filter-repo`.
+  Written mainly in Rust, under MIT License.
+- [Furgit](https://villosa.lindenii.org/furgit//repos/furgit/)
+  ([GitHub mirror](https://github.com/runxiyu/furgit))
+  is a fast Git library in pure Go (and a little bit of optional Go Assembly).
+  Written for [Lindenii Villosa](https://villosa.lindenii.org/villosa//repos/villosa/)
+  (successor to [Lindenii Forge](https://forge.lindenii.org/forge/-/repos/server/)),
+  a software forge primarily designed for self-hosting
+  by small organizations and individuals.
+  Under AGPL 3.0 license.
+- [git-embigenner](https://github.com/veqqq/git-embigenner)
+  is a very simple shell script to cheat a highscore on GitHub,
+  which will spam commits to populate your profile's contribution graph.
+    - Compare with [Git Draw](https://github.com/ben174/git-draw),
+	  a Chrome extension which will allow you to freely draw on your GitHub heatmap,
+	  mentioned in [Git Rev News Edition #12](https://git.github.io/rev_news/2016/02/10/edition-12/)<br>
+	  and [gitfiti](https://github.com/gelstudios/gitfiti),
+	  a tool for crafting graffiti in a GitHub commit history calendar,
+	  mentioned in [Git Rev News Edition #41](https://git.github.io/rev_news/2018/07/18/edition-41/).
+    - Contrast [Vigilante Justice on GitHub: GitHub Graffiti](https://trufflesecurity.com/blog/vigilante-justice-on-github) by Dylan Ayrey,
+	  mentioned in [Git Rev News Edition #118](https://git.github.io/rev_news/2024/12/31/edition-118/),
+	  about how you can paint funny pixel art (graffiti) with fake commit Git histories
+	  on spammer/phisher’s GitHub profiles (on their activity heatmap plot)
+
 
 ## Releases
 
