From 74d5ef9c5cb95e5daf69103e5d43208df864cf2a Mon Sep 17 00:00:00 2001 From: Bruno Brito Date: Wed, 23 Jul 2025 13:08:52 +0100 Subject: [PATCH 01/45] rn-125: Add new Tower releases --- rev_news/drafts/edition-125.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index 8a728308e..3a88672b8 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -48,7 +48,8 @@ __Git tools and sites__ ## Releases - +- Tower for Mac [13.1](https://www.git-tower.com/release-notes/mac?show_tab=release-notes) +- Tower for Windows [9.1](https://www.git-tower.com/release-notes/windows?show_tab=release-notes) - [YT video](https://youtu.be/4pNRUz0bNIU) ## Credits From 976f50c8c45246f2d4fbf881f634c26c88a9c9a6 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Fri, 25 Jul 2025 15:42:26 +0200 Subject: [PATCH 02/45] add a link to deepwiki.com/git/git --- Hacking-Git.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Hacking-Git.md b/Hacking-Git.md index c43106897..477c3252a 100644 --- a/Hacking-Git.md +++ b/Hacking-Git.md @@ -32,6 +32,8 @@ suggest improvements. Thanks! * [Fabien Sanglar's Git Source Code Review](https://fabiensanglard.net/git_code_review/architecture.php) +* [DeepWiki git/git, an AI generated introduction level overview](https://deepwiki.com/git/git) + * [Boost Your Programming Skills by Reading Git's Code](https://www.freecodecamp.org/news/boost-programming-skills-read-git-code/) ## Getting started hacking and contributing From 2cae9154fb8fd2f93b33784dc72e5542c54f088e Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Fri, 25 Jul 2025 20:02:59 +0200 Subject: [PATCH 03/45] rn-125: add git-phoenix tool --- rev_news/drafts/edition-125.md | 1 + 1 file changed, 1 insertion(+) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index 3a88672b8..cff129335 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -46,6 +46,7 @@ __Easy watching__ __Git tools and sites__ +- [git-phoenix](https://github.com/yaitskov/git-phoenix) does repository recovery. ## Releases - Tower for Mac [13.1](https://www.git-tower.com/release-notes/mac?show_tab=release-notes) From 14599936e099a3d8787ef11a392f203adbd2f791 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sat, 26 Jul 2025 10:32:23 +0200 Subject: [PATCH 04/45] Hacking-Git: clarify acceptable content --- Hacking-Git.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/Hacking-Git.md b/Hacking-Git.md index 477c3252a..7dd16d665 100644 --- a/Hacking-Git.md +++ b/Hacking-Git.md @@ -3,12 +3,15 @@ layout: default title: Hacking Git --- -The goal of this document is not to be a tutorial, but rather to -point to interesting material that has already been written. - -The goal is also not to list all the articles about Git or its -internals. There are a lot of good resources, including free -[books](http://git-scm.com/book/en/v2/), about that elsewhere. +The goal of this document is not to be a tutorial, but rather to point +to interesting material that has already been written. + +The goal is also not to list all the articles, tools or resources +about Git or its internals. There are a lot of good resources, +including [free books](http://git-scm.com/book/en/v2/), and the +[archive of our newsletter](https://git.github.io/rev_news/archive/), +about that elsewhere. So on this page we focus on what is the most +interesting for developers starting to work on Git. Contributions are welcome though! Please contact us on the Git Mailing list (at [git@vger.kernel.org](mailto:git@vger.kernel.org)) or open an From d32fb54069e32f0cbf1b09bb053351ad11633075 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Wed, 30 Jul 2025 11:48:36 +0200 Subject: [PATCH 05/45] rn-125: add Git Mini Summit mini article --- rev_news/drafts/edition-125.md | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index cff129335..4423ab731 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -17,9 +17,22 @@ This edition covers what happened during the months of June 2025 and July 2025. ## Discussions - + +* [[ANNOUNCE] Git Mini Summit at Open Source Summit Europe, Amsterdam, August 28th](https://lore.kernel.org/git/aGwHt9HCd86hVuKh@pks.im/) + + Patrick Steinhardt announced a Git Mini Summit co-located with the + [Open Source Summit Europe](https://events.linuxfoundation.org/open-source-summit-europe/) + in Amsterdam on August 28th 2025. + + There will be lightning talks and some time for people to + connect. For the lightning talks proposals should be sent to + Patrick, while the possibility to have remote talks is still + investigated. + + [Registration is open](https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#git-mini-summit-2025) + for only the Git Mini Summit and for the Open Source Summit Europe including the Git Mini Summit. + +* [[PATCH v4 0/3] send-email: add oauth2 support and fix outlook breaking threads](https://lore.kernel.org/git/PN3PR01MB9597A83D537E3AE96144227EB8BA2@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM/) + + Last April, Aditya Garg sent a patch series containing three main + changes to `git send-email`. He mentioned that he was sending the + email series using the very patches he is proposing, via Outlook. + + The first patch, which was a rebased version of + [an earlier patch by Julian Swagemakers](https://lore.kernel.org/git/20250125190131.48717-1-julian@swagemakers.org/) + added support for OAuth2 authentication, which started to be + required by Microsoft. Julian's patch unfortunately had been waiting + for review for over a year before Aditya picked it up. + + The second patch fixed thread breaking caused by Outlook's + proprietary Message-ID handling. + + The final patch added a new option for generating passwords, such as + OAuth2 tokens, via an external script. + + Junio Hamano, the Git maintainer, reviewed the three patches saying + he liked the commit messages, documentation and code comments even + though he suggested a few small style improvements to the code + style, and a number of grammar and formatting changes to the + documentation. + + He also asked for reviews from others as he said he was not familiar + with the `Authen::SASL` library. + + Aditya replied to Junio's review acknowledging the need for more + reviews and saying that OAuth2 was a significant and more secure + technology. He then took the initiative to Cc Greg Kroah-Hartman, + who wrote a precursor of `git send-email` for the Linux kernel. + + M Hickford also replied to Aditya expressing enthusiasm for the work + but wondering why the v4 version of the patch series was sent in a + new email thread rather than as a reply to the previous version. + + brian m. carlson commented on the second patch saying that replacing + message IDs like Outlook does is technically allowed by + standards. He raised concerns about hardcoding only two Outlook + server hostnames, and suggested adding configuration options for + Message-ID generation modes. + + Julian Swagemakers then pointed out that the goal of the third patch + could already be achieved using Git's existing custom credential + helper mechanism. Aditya confirmed this worked and said he was + unaware of this feature, which led to the decision to drop the third + patch. Recognizing that the existing feature was poorly + discoverable, the discussion led to improvements in Git's + documentation, adding clearer examples of using credential helpers + for OAuth2 tokens. + + Erik Huelsmann, the maintainer of the `Authen::SASL` Perl module, + joined the conversation after Aditya emailed him directly + referencing a GitHub issue about the lack of OAuth2 support in + `Authen::SASL`. In that issue Erik had + [commented that he would be happy to support XOAUTH2](https://github.com/gbarr/perl-authen-sasl/issues/18#issuecomment-2453040190), + but needed a patch and a way to test it. + + Aditya and Julian then worked together, with guidance from Erik, to + add the necessary XOAUTH2 and OAUTHBEARER support directly into + `Authen::SASL`. Shortly after, a new version of the `Authen::SASL` + module was officially released with this new functionality. This + successful collaboration meant the first patch in the series, which + was a workaround for the missing library support, was no longer + needed and was subsequently dropped. Instead the new version of + `Authen::SASL` started to benefit all Perl users. + + Greg Kroah-Hartman echoed what brian had suggested about using a + configurable solution in the second patch. Greg noted that the + initial approach would not cover company-hosted Outlook servers. + + That suggestion was then refined by Junio Hamano, who proposed a + concrete implementation for the new option by providing an example + patch. The final `--[no-]outlook-id-fix` option auto-detects known + Outlook servers but allows manual override for other deployments. + + After several iterations on its name and behavior, Aditya submitted + a final, simplified patch series (v6). It now contained only the + single, refined patch to fix Outlook thread breaking, with the other + two patches having been made obsolete by the `Authen::SASL` library + update and the use of existing Git features. + + Aditya's patch was merged and released as part of Git v2.50.0. - +## Developer Spotlight:Usman Akinyemi + +_Editor’s note: This edition features a retrospective interview with a +contributor who contributed to Git through a mentoring program. We hope +the reflections shared by the Outreachy contributor will provide an +insightful perspective that benefits the community. As always, we +welcome your thoughts and feedback!_ + +* **Who are you and what do you do?** + + I’m Usman Akinyemi, a final-year CS and AI student, and an open-source + contributor passionate about Linux, distributed systems, and developer + tools. I’ve contributed to core projects like Git, systemd, LLVM, and + LibreOffice. During [my Outreachy internship](https://uniqueusman.hashnode.dev/my-outreachy-internship-experience-at-git), + I improved Git’s v2 protocol by adding OS-level metadata for better + diagnostics and security. + + Currently, I’m a [Google Summer of Code contributor](https://summerofcode.withgoogle.com/programs/2025/projects/wBCitF8F) + building a containerized pipeline for medical imaging using Kaapana, + Kubernetes and Airflow. I am also currently working on creating a + new subtype for RISC-V assembly instructions through the + Linux Foundation’s LFX program. + + Outside code, I mentor new contributors, volunteer with DesignIT and + LEAD and CODE to teach digital skills, and organize a tech webinar for + Nigerian students. I’ll be [speaking at Git Merge 2025](https://git-merge.com/#usman-akinyemi), + sharing insights from my open-source journey. I believe in the power of + community, collaboration, and curiosity to build a career that crosses + borders. + +* **How did you initially become interested in contributing to Git, + and what motivated you to choose it as your Outreachy project?** + + Though I have been contributing to other projects before applying for + Outreachy (Dec 2024), I was just a user of the Git project. When it + comes to the Outreachy contribution period when I had to pick a + project, I picked both Git and LibreOffice. I picked Git as it is a + project I use every time, also the thought of contributing to a + project used by almost all the developers in the whole world was + definitely a dream coming true. To also maximize my getting selected + for Outreachy, I picked Git because it is written in C programming + which many other participants are always scared to pick (going for the + hard thing). The story did not end there as I got selected for both + LibreOffice and Git and I had to choose one as my Outreachy projects. + It was a hard decision but I picked it mainly because the Git + community is a community where it is so easy to communicate with other + team members, it is a community where I clearly know who is who and + what they do in the community. Also Git is more well recognised. + +* **How do you feel your contribution has impacted the Git community + or the broader open source ecosystem?** + + [My contribution](https://lore.kernel.org/git/20250215155130.1756934-1-usmanakinyemi202@gmail.com/) + makes a fundamental improvement to the Git v2 protocol by enabling + Git clients to share their operating system information via the user + agent string. This helps platforms like GitHub, GitLab, and others + gain visibility into which OS environments are interacting + with their servers. It significantly improves debugging, security + auditing, and telemetry, helping maintainers understand usage patterns + and tailor support or upgrade strategies accordingly. Since this + change is part of the core Git client, it means it is used by all Git + users. I’m proud to have contributed something with such + wide-reaching, foundational impact. + +* **Is there any aspect of Git that you now see differently after + having contributed to it?** + + Before contributing to Git, I saw it as a complex tool that "just + works". Although I knew Git was different from GitHub, I struggled to + clearly differentiate between the two. But after contributing, I could + clearly differentiate between the two and I now see Git as a carefully + designed software project with a strong emphasis on performance, + cross-platform compatibility, and community-driven development. + + I’ve come to appreciate the level of thought and care that goes into + every change, from writing clean patches and commit messages to + engaging in technical discussions and defending your design decisions. + + Contributing to Git isn’t also about hierarchical review; instead, + it’s a collaborative process where every contributor is expected to + take full ownership of their patches, understand the problem they are + trying to fix, the solution and explain their rationale clearly by + writing clean patches, commit messages and engaging in technical + discussions and defending your design decisions. In fact, there have + been moments when some of my contributions led to insights even long + time contributors hadn’t considered, including Junio Hamano. That + boosted my confidence not just in contributing to Git, but to other + software projects as well i.e I can get my patches accepted anywhere, + I just need to convince others that it actually solves a problem. + +* **How do you balance your contributions with other responsibilities + like work or school?** + + Seriously, it has not been easy, most of my contributions to all + open source projects have always been during college. But, I have sort + of made contributions to open source as one important aspect of my + life and also as a way to learn new technologies and also practice + whatever new skills I learnt. Contributing to projects millions of + people use is also definitely rewarding and satisfying. + +* **Can you share how Outreachy helped enhance your technical and + non-technical skills (like communication, project management, etc.)?** + + Technically, I have been able to improve my C programming and bash + scripting skills. Also reading and understanding very large codebases + like Git. Of course now, I can call myself an expert in using Git as a + tool itself. + + To contribute to Git, you must be able to communicate well as all the + Git workflows happen remotely and over mailing lists. Most of the time + in the Git community, it is not about the correctness of your code, it + is about how well you can communicate your rationale to the community + before your patches can be accepted. So, over time, as a Git + contributor, my communication skills in a technical environment have + really improved. + + I have also learnt to write clean code, organize my changes into well + formatted patches and write clear commit messages. + +* **What was your biggest takeaway or learning from Outreachy that + you now apply regularly in your work?** + + I’d say my biggest takeaway from Outreachy is learning how to write + clear, structured commit messages. Git commits, like those in the + Linux kernel, follow a thoughtful format: describe the current state, + the problem, and the fix. From reading most of the commit messages in + Git, you would have understood and been to visualize what the changes + will look like. It also makes it easy to track the changes to other + prerequisite commits. I have been using the Git commit messages format + in other projects and I really love it. + +* **What was the biggest challenge you faced during your contributions + to Git, and how did you overcome it?** + + I think the challenge which I initially faced is sending patches to + Git, not really a big challenge though as I was able to make my first + patch in a few days after joining the community. And the reason is + that Git does not use GitHub or GitLab, something someone would have + thought they will be using. Git uses a mailing list just like the + Linux kernel. While writing this, I remember that I had a challenge + retrieving patches from the mailing list as my project depends on some + patches that were sent by my mentor previously. I had to use `git am`, + something I never used before. Help from my mentor really helped + and reading through the the "[Hacking Git](https://git.github.io/Hacking-Git/)" + page. + +* **Have you thought about mentoring new GSoC / Outreachy students?** + + Yeah, I am planning to put in as a mentor for the coming Outreachy + period and hopefully for GSoC also. I will be starting as a co-mentor + though. + +* **If you could get a team of expert developers to work full time on + something in Git for a full year, what would it be?** + + Smile, I will definitely say the Rustication of some parts of Git + which has been going on currently, I think one that has already been + integrated to Git is [libgit-rs](https://lore.kernel.org/git/cover.1738187176.git.steadmon@google.com/). + Rust seems to be a language that focuses more on safety/security + and safety/security in Git is very important. I am also a Rustacean + so I should be able to help hopefully if that happens. + +* **If you could remove something from Git without worrying about + backwards compatibility, what would it be?** + + I really do not have anything in mind for now. + +* **What upcoming features or changes in Git are you particularly + excited about?** + + I think it is one of the [GSoC projects by Lucas](https://summerofcode.withgoogle.com/programs/2025/projects/fGgMYHwl). + I have been passively following the project. It is about introducing + a new Git sub-command (currently intended to be called `git repo-info`) + that will centralize data currently retrieved by `git rev-parse` in a + JSON format. + +* **What is your favorite Git-related tool/library, outside of Git + itself?** + + I think is GitHub and GitLab, if I have to choose one, I will say GitHub. + +* **What is your toolbox for interacting with the mailing list and for + development of Git?** + + I started with [GitGitGadget](https://gitgitgadget.github.io/) initially + just to get my patches to the mailing list faster but, along the line + I switched to `git send-email` and really, it is more flexible and easy + to use than I thought of it. For my machine, I basically use Arch Linux + and Neovim for my text editor. + +* **How do you envision your own involvement with Git or other open + source projects in the future?** + + As I said earlier, open source has really been part of my life and it + has really helped me a lot in improving my skills, meeting new people + and even making some few bucks through internships. After my + internship at Outreachy, I did send patches to the Git community and I + planned to keep doing that. After Outreachy, I have contributed to a + few other projects like RISCV and OSIPI (through GSoC). I currently + mentor people who want to start their open source journey and I plan + to do more of it. I planned to keep contributing to open source + projects and hopefully get a job in open source. + +* **What is your advice for people who want to start Git development? + Where and how should they start?** + + I have been in many open source projects and see how their workflows + are, I will definitely say Git is one of the easiest and most + interesting projects to contribute to. The community members are + really supportive. Seriously, it is one of the best open source + communities I have been to. The best place to start is going through + the "[Hacking Git](https://git.github.io/Hacking-Git/)" page. It has + all the information on how to start contributing and you can make + your first contribution to Git. You should generally start with a + microproject which aims to introduce you to the Git contribution + workflow. Everything can be found above. Making your first contribution + to Git is actually very much easier than you might have thought. + Also, do not be scared to ask for help, Git developers are always ready to render help. + +* **Would you recommend other students or contributors to participate in + the GSoC, Outreachy or other mentoring programs, working on Git? + Why? Do you have advice for them?** + + Definitely, Outreachy and GSoC are very much interesting mentoring + programs to start your open source journey. They both really make it + easy to start contributing to open source. You get assigned to mentors + who are experts in open source and the organization. It is a way to get + skills you will never be able to get in your classroom and skills + needed to thrive and excel in the software engineering world. Apart + from skills, it is a way to have proof of work before graduation and + also gain global recognition. As I have said, Git is a well known and + recognized software project in the whole world, contributing to it is + an achievement on its own. + + _Shout session_ + + I would like to shout out to all Git contributors, you are doing a + great job! I would also like to shout out to my Outreachy mentor + Christian Couder, he was really supportive during my Outreachy + program! Thanks to the Git Rev teams also! + ## Other News From f7a1a4bf5d64af38adc167b2c5e7bd7cac1e04bd Mon Sep 17 00:00:00 2001 From: Markus Jansen Date: Fri, 1 Aug 2025 23:58:45 +0200 Subject: [PATCH 20/45] rn-125: provide a few tiny fixes and rephrasings --- rev_news/drafts/edition-125.md | 46 +++++++++++++++++----------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index f24cd88e7..ed2ace0fa 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -22,10 +22,10 @@ This edition covers what happened during the months of June and July 2025. * 20 years ago: [Meet the new maintainer..](https://lore.kernel.org/git/Pine.LNX.4.58.0507262004320.3227@g5.osdl.org/) - On July 26 Jul 2005, so 20 years ago, Linus Torvalds announced on + On July 26 2005, so 20 years ago, Linus Torvalds announced on the mailing list that Junio Hamano accepted the maintainership of the Git project and that Junio "was the obvious choice". Linus said - he wasn't dropping Git but he just prefered working on it as a + he wasn't dropping Git but he just preferred working on it as a contributor. Junio replied with an [A note from the new GIT maintainer](https://lore.kernel.org/git/7vmzo8ss2l.fsf@assigned-by-dhcp.cox.net/) @@ -48,7 +48,7 @@ This edition covers what happened during the months of June and July 2025. investigated. [Registration is open](https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#git-mini-summit-2025) - for only the Git Mini Summit and for the Open Source Summit Europe including the Git Mini Summit. + for both the Git Mini Summit only and for the Open Source Summit Europe including the Git Mini Summit. ### Reviews @@ -57,11 +57,11 @@ This edition covers what happened during the months of June and July 2025. Last April, Aditya Garg sent a patch series containing three main changes to `git send-email`. He mentioned that he was sending the - email series using the very patches he is proposing, via Outlook. + email series using the very patches he was proposing, via Outlook. The first patch, which was a rebased version of [an earlier patch by Julian Swagemakers](https://lore.kernel.org/git/20250125190131.48717-1-julian@swagemakers.org/) - added support for OAuth2 authentication, which started to be + adding support for OAuth2 authentication, which started to be required by Microsoft. Julian's patch unfortunately had been waiting for review for over a year before Aditya picked it up. @@ -74,7 +74,7 @@ This edition covers what happened during the months of June and July 2025. Junio Hamano, the Git maintainer, reviewed the three patches saying he liked the commit messages, documentation and code comments even though he suggested a few small style improvements to the code - style, and a number of grammar and formatting changes to the + style plus a number of grammar and formatting changes to the documentation. He also asked for reviews from others as he said he was not familiar @@ -117,7 +117,7 @@ This edition covers what happened during the months of June and July 2025. module was officially released with this new functionality. This successful collaboration meant the first patch in the series, which was a workaround for the missing library support, was no longer - needed and was subsequently dropped. Instead the new version of + needed and was subsequently dropped. Instead, the new version of `Authen::SASL` started to benefit all Perl users. Greg Kroah-Hartman echoed what brian had suggested about using a @@ -145,7 +145,7 @@ This edition covers what happened during the months of June and July 2025. ### Support --> -## Developer Spotlight:Usman Akinyemi +## Developer Spotlight: Usman Akinyemi _Editor’s note: This edition features a retrospective interview with a contributor who contributed to Git through a mentoring program. We hope @@ -185,13 +185,13 @@ welcome your thoughts and feedback!_ project I use every time, also the thought of contributing to a project used by almost all the developers in the whole world was definitely a dream coming true. To also maximize my getting selected - for Outreachy, I picked Git because it is written in C programming + for Outreachy, I picked Git because it is written in C, which many other participants are always scared to pick (going for the hard thing). The story did not end there as I got selected for both LibreOffice and Git and I had to choose one as my Outreachy projects. It was a hard decision but I picked it mainly because the Git community is a community where it is so easy to communicate with other - team members, it is a community where I clearly know who is who and + team members, and it is a community where I clearly know who is who and what they do in the community. Also Git is more well recognised. * **How do you feel your contribution has impacted the Git community @@ -250,19 +250,19 @@ welcome your thoughts and feedback!_ Technically, I have been able to improve my C programming and bash scripting skills. Also reading and understanding very large codebases - like Git. Of course now, I can call myself an expert in using Git as a + like Git. Of course now I can call myself an expert in using Git as a tool itself. - To contribute to Git, you must be able to communicate well as all the + To contribute to Git, you must be able to communicate well, as all the Git workflows happen remotely and over mailing lists. Most of the time - in the Git community, it is not about the correctness of your code, it + in the Git community it is not about the correctness of your code -- it is about how well you can communicate your rationale to the community before your patches can be accepted. So, over time, as a Git contributor, my communication skills in a technical environment have really improved. I have also learnt to write clean code, organize my changes into well - formatted patches and write clear commit messages. + formatted patches, and write clear commit messages. * **What was your biggest takeaway or learning from Outreachy that you now apply regularly in your work?** @@ -285,10 +285,10 @@ welcome your thoughts and feedback!_ that Git does not use GitHub or GitLab, something someone would have thought they will be using. Git uses a mailing list just like the Linux kernel. While writing this, I remember that I had a challenge - retrieving patches from the mailing list as my project depends on some + retrieving patches from the mailing list as my project depended on some patches that were sent by my mentor previously. I had to use `git am`, - something I never used before. Help from my mentor really helped - and reading through the the "[Hacking Git](https://git.github.io/Hacking-Git/)" + something I never used before. Help from my mentor really helped, + as well as reading through the "[Hacking Git](https://git.github.io/Hacking-Git/)" page. * **Have you thought about mentoring new GSoC / Outreachy students?** @@ -303,8 +303,8 @@ welcome your thoughts and feedback!_ Smile, I will definitely say the Rustication of some parts of Git which has been going on currently, I think one that has already been integrated to Git is [libgit-rs](https://lore.kernel.org/git/cover.1738187176.git.steadmon@google.com/). - Rust seems to be a language that focuses more on safety/security - and safety/security in Git is very important. I am also a Rustacean + Rust seems to be a language that focuses more on safety/security, + and safety/security is very important in Git. I am also a Rustacean so I should be able to help hopefully if that happens. * **If you could remove something from Git without worrying about @@ -324,7 +324,7 @@ welcome your thoughts and feedback!_ * **What is your favorite Git-related tool/library, outside of Git itself?** - I think is GitHub and GitLab, if I have to choose one, I will say GitHub. + I think it's both GitHub and GitLab -- if I have to choose one, I will say GitHub. * **What is your toolbox for interacting with the mailing list and for development of Git?** @@ -333,7 +333,7 @@ welcome your thoughts and feedback!_ just to get my patches to the mailing list faster but, along the line I switched to `git send-email` and really, it is more flexible and easy to use than I thought of it. For my machine, I basically use Arch Linux - and Neovim for my text editor. + and Neovim as my text editor. * **How do you envision your own involvement with Git or other open source projects in the future?** @@ -343,8 +343,8 @@ welcome your thoughts and feedback!_ and even making some few bucks through internships. After my internship at Outreachy, I did send patches to the Git community and I planned to keep doing that. After Outreachy, I have contributed to a - few other projects like RISCV and OSIPI (through GSoC). I currently - mentor people who want to start their open source journey and I plan + few other projects like RISC-V and OSIPI (through GSoC). I currently + mentor people who want to start their open source journey, and I plan to do more of it. I planned to keep contributing to open source projects and hopefully get a job in open source. From 252d0276abe326542f036f559fe8d74228167f56 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Nar=C4=99bski?= Date: Sat, 2 Aug 2025 02:21:03 +0200 Subject: [PATCH 21/45] rn-125: Add links to various news, articles, sites, and tools --- rev_news/drafts/edition-125.md | 191 +++++++++++++++++++++++++++++++++ 1 file changed, 191 insertions(+) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index f24cd88e7..d6111b479 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -391,16 +391,207 @@ welcome your thoughts and feedback!_ __Various__ ++ [[LWN.net] A set of Git security-fix releases](https://lwn.net/Articles/1029182/) + by Jonathan Corbet on LWN\.net, and
+ [Multiple vulnerabilities fixed in Git](https://www.openwall.com/lists/oss-security/2025/07/08/4) + by Taylor Blau on oss-security mailing list ++ [[ANNOUNCE] Git v2.50.1 and friends](https://public-inbox.org/git/xmqqzfdevcov.fsf@gitster.g/t/#u) + by Junio C Hamano on the git mailing list. ++ [Launchpad](https://launchpad.net/) is [phasing out Bazaar code hosting](https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189). + This post provides link to the [Migrate a Repository From Bazaar to Git](https://jugmac00.github.io/blog/migrate-a-repository-from-bazaar-to-git/) article. + __Light reading__ ++ [Artisanal Handcrafted Git Repositories](https://drew.silcock.dev/blog/artisanal-git/) + by Drew Silcock on drew's dev blog. + This article talks about how to handmake your Git repositories without using git commands. + You might also learn a bit more about how Git works under the hood during the process. ++ [How to use git worktree effectively with Python projects](https://www.andreagrandi.it/posts/how-to-use-git-worktree-effectively-with-python-projects/) + (with the help of a simple [git-add-worktree.sh](https://gist.github.com/andreagrandi/542b438bf0017d93aff2b640037e3ce1) Bash script) + by Andrea Grandi on his blog. ++ [Managing Multiple Claude Code Sessions Without Worktrees](https://blog.gitbutler.com/parallel-claude-code/) + by Scott Chacon on Butler's Log (GitButler Blog). + With [Claude Code](https://www.anthropic.com/claude-code)'s new [lifecycle hooks](https://docs.anthropic.com/en/docs/claude-code/hooks), + [GitButler](https://gitbutler.com/) Git client auto-sorts simultaneous AI coding into separate branches, + without manual [use of `git worktree`](https://www.anthropic.com/engineering/claude-code-best-practices#c-use-git-worktrees). + With this feature you can write three features, and get three clean branches. ++ [wtp: A Better Git Worktree CLI Tool](https://dev.to/satococoa/wtp-a-better-git-worktree-cli-tool-4i8l) + by Satoshi Ebisawa on DEV\.to. + The [wtp](https://github.com/satococoa/wtp) tool was created to make + working with multiple tasks in parallel using [Claude Code](https://www.anthropic.com/claude-code) + easier than with `git worktree`. ++ [Automated repo maintenance via GitHub Copilot coding agent](https://blog.pamelafox.org/2025/07/automated-repo-maintenance-with-github.html) + by Pamela Fox on her Blogger-based blog. ++ [Git Worktrees: Git Done Right](https://www.nickyt.co/blog/git-worktrees-git-done-right-2p7f/) + by Nick Taylor on Just Some Dev blog (and also [on DEV\.to](https://dev.to/nickytonline/git-worktrees-git-done-right-2p7f)). ++ [I Lost My Git Stash, So I Built a Tool (VS Code Extension) to Share It](https://dev.to/karandeepsingh7070/i-lost-my-git-stash-so-i-built-a-tool-to-share-it-27bn) + by Karandeep Singh on DEV\.to. ++ [Git: share a full repository as a file with `git fast-export`](https://adamj.eu/tech/2025/07/15/git-share-fast-export/) + by Adam Johnson on his blog + (for some reason the post does not mention the alternative of using + [`git bundle`](https://git-scm.com/docs/git-bundle)). + + Adam Johnson is the author of "[Boost Your Git DX](https://adamchainz.gumroad.com/l/bygdx)" book, + first mentioned in [Git Rev News Edition #104](https://git.github.io/rev_news/2023/10/31/edition-104/), + then its updates in [#110](https://git.github.io/rev_news/2024/04/30/edition-110/) + and [#119](https://git.github.io/rev_news/2025/01/31/edition-119/). ++ [Conventional Commits makes me sad](https://srazkvt.codeberg.page/posts/2025-07-06-conventional-commits-makes-me-sad.html) + by Sarah Mathey on her Codeberg Pages powered Sarah's Website blog.
+ The [Conventional Commits](https://www.conventionalcommits.org/) specification + was first mentioned in [Git Rev News Edition #52](https://git.github.io/rev_news/2019/06/28/edition-52/). ++ [Git experts should try Jujutsu](https://pksunkara.com/thoughts/git-experts-should-try-jujutsu/) + by Pavan Sunkara on his personal blog.
+ [Jujutsu (`jj`)](https://github.com/martinvonz/jj) is a version control system + first mentioned in [Git Rev News Edition #85](https://git.github.io/rev_news/2022/03/31/edition-85/). ++ [Jujutsu For Busy Devs](https://maddie.wtf/posts/2025-07-21-jujutsu-for-busy-devs) and + by Madeleine Mortensen on her personal blog. ++ [Using Radicle CI for Development](https://radicle.xyz/2025/07/23/using-radicle-ci-for-development) + by Lars Wirzenius on Radicle Blog.
+ [Radicle](https://radicle.xyz/) is the distributed git hosting system, + first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). ++ [Cutting GitHub out of the loop](https://www.circusscientist.com/2025/07/23/cutting-github-out-of-the-loop/) + (by deploying to VPS with Git and SSH). + Written by tomjuggler on The Circus Scientist Site. ++ [Super Easy* 2-Stage Git Deployment](https://ratfactor.com/cards/super-easy-2-stage-git-deployment) + by Dave Gauer on Dave's Virtual Box of Cards. ++ [Guest Post: How I Scanned all of GitHub’s “Oops Commits” for Leaked Secrets](https://trufflesecurity.com/blog/guest-post-how-i-scanned-all-of-github-s-oops-commits-for-leaked-secrets) + by Sharon Brizinov on The Dig, the Truffle Security blog. ++ [Top 17 Essential Git Tools for Enhanced Developer Productivity](https://dev.to/vaib/top-17-essential-git-tools-for-enhanced-developer-productivity-7f3) + by vAlber on DEV\.to. + + __Git tools and sites__ ++ [DiffX - Next-Generation Extensible Diff Format](https://diffx.org/): + describes problem with Unified Diff format, and proposes as a solution + a new file format specification for Extensible Diffs, + fully backwards-compatible with existing tools, + while also being future-proof and remaining human-readable. - [git-phoenix](https://github.com/yaitskov/git-phoenix) does repository recovery. ++ [wtp (Worktree Plus)](https://github.com/satococoa/wtp) is a Git worktree management tool + that extends git's worktree functionality with + automated setup, branch tracking, and project-specific hooks. + Written in Go, under the MIT license. ++ [GitNifty](https://gitnifty.js.org/index.html) is a robust and promise-based Git utility for Node.js, + offering developers smart, automation-ready commands for common Git operations. + Created for building CLI tools, automation scripts, or custom Git workflows. + Written in TypeScript, and released under the Apache License. ++ [difit](https://github.com/yoshiko-pg/difit) is a CLI tool + that lets you view and review local git diffs with a GitHub-style viewer + (in a browser). Written in TypeScript, under MIT license.
+ See [difit: Preview GitHub-like diffs locally before you push](https://dev.to/unhappychoice/difit-preview-github-like-diffs-locally-before-you-push-37gc) + by Yuji Ueki on DEV\.to. ++ [Flint](https://flintable.com/docs/flint/) is a Git-integrated code formatter + that lets each developer work in their preferred style locally, + while maintaining a consistent style remotely. + By automatically applying “local” and “remote” formatting passes during pull and push operations, + Flint prevents formatting noise in commits and code reviews. + It is currently in _alpha_ and is available exclusively on npm. + Written in Bash, under MIT license. ++ [DotProj](https://dotproj.ac-jr.com/) is a developer-centric CLI tool + designed to manage project-specific configuration files with Git versioning. + It helps keep your development environment settings organized, versioned, and synchronized + across multiple machines and projects. + DotProj uses Git commands (commit, push, pull, clone) making it intuitive for developers. + Written as Bash shell script, under MIT license. ++ [git-remote-sqlite](https://github.com/chrislloyd/git-remote-sqlite) + is a [Git protocol helper](https://git-scm.com/docs/gitremote-helpers) + that helps you store a Git repository in a SQLite database. + Written in Zig, under MIT license. ++ [Backlog.md](https://backlog.md/) is a tool that turns any folder with a Git repo + into a self‑contained project board, powered by plain Markdown files + and a zero‑config CLI. Written in TypeScript, under MIT license. AI ready. ++ [git-resolve.sh](https://elixir.bootlin.com/linux/v6.16-rc3/source/scripts/git-resolve.sh) + is a Bash script that resolves a short git commit ID to its full SHA-1 hash, + which is particularly useful for fixing references in commit messages. + Under GPL-2.0 license. ++ [GitHub Trends](https://www.githubtrends.io/) is a service that + uses GitHub API to bring you insightful metrics on your contributions, + broken by repository and language. ++ [DeepWiki](https://deepwiki.com/): AI-generated docs for any repo. + This service turns any public GitHub repo into up-to-date documentation you can talk to + (see for example [DeepWiki: git/git](https://deepwiki.com/git/git). + DeepWiki is the free public version of [Devin Wiki](https://docs.devin.ai/work-with-devin/devin-wiki) and [Devin Search](https://docs.devin.ai/work-with-devin/devin-search).
+ There are a few silimar projects, like + [Open Source DeepWiki](https://github.com/AsyncFuncAI/deepwiki-open) and + [OpenDeepWiki](https://github.com/AIDotNet/OpenDeepWiki). ++ [GitHub Repository Maintenance Agent](https://github.com/pamelafox/github-repo-maintainer-agent/) + is an AI-powered agent for triaging failed [Dependabot](https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide) pull requests + across one GitHub repositories. The agent uses [Pydantic AI](https://ai.pydantic.dev/) + for LLM-based decisions and the GitHub API for repository, PR, and issue management. + Written in Python, under MIT license. ++ [tangled](https://tangled.sh/) is new social-enabled git collaboration platform + built on [AT Protocol](https://atproto.com/) (that powers the Bluesky social network). + Written in Go, under MIT license; note that it is in alpha stage of development.
+ Compare with: + + [Radicle](https://radicle.xyz/), a peer-to-peer, local-first code collaboration stack built on Git + (first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/)). + + [ForgeFed](https://forgefed.org/) (formerly GitPub), a federation protocol for software forges + (first mentioned in [Git Rev News Edition #69](https://git.github.io/rev_news/2020/11/27/edition-69/)). + + [`git-ssb`](https://scuttlebot.io/apis/community/git-ssb.html) + (see the [git-ssb-intro](https://github.com/hackergrrl/git-ssb-intro) guide), a + decentralized Git repo hosting and issue tracking on [Secure-ScuttleButt (SSB)](https://www.scuttlebutt.nz/) + (first mentioned in [Git Rev News Edition #26](https://git.github.io/rev_news/2017/04/19/edition-26/). + + [gitstr (`git str`)](https://github.com/fiatjaf/gitstr), + a tool to send and receive Git patches + over [Nostr](https://nostr.com/), using [NIP-34](https://github.com/nostr-protocol/nips/pull/997) + (first mentioned in [Git Rev News Edition #109](https://git.github.io/rev_news/2024/03/31/edition-109/)). ++ [Git With Me](https://sr.ht/~meejah/git-withme/) is a tool for + peer-to-peer, encrypted, ephemeral Git collaboration. + `git withme` provides a way for a single host to invite numerous peers + with short, one-time secure codes. The peers connect directly via + [Dilated Magic Wormhole channels](https://meejah.ca/blog/fow-wormhole-forward), + allowing collaborators to `git clone git://localhost/`. ++ [Radicle Desktop](https://desktop.radicle.xyz/) is a desktop application + that lets you interact with [Radicle](https://radicle.xyz/), + a peer-to-peer code collaboration and publishing stack. + Written in TypeScript for Node.js and Rust, using the Tauri framework. + Under GPLv3 license. ++ [GitBug: Git Learning Simulator](https://github.com/dvig14/gitbug) + is a CLI app that teaches Git through hands-on bug fixing. + It uses a realistic merge conflict scenario with visual feedback at every step + The goal of the app is to help you learn by doing, not just reading. + Written in Python, under MIT license, in early stage (alpha).
+ Compare with: + + [Learn Git Branching](https://learngitbranching.js.org/), + mentioned first in [Git Rev News Edition #30](https://git.github.io/rev_news/2017/08/16/edition-30/). + + [Git Gud](https://nic-hartley.github.io/git-gud/), a visual web-based Git simulator, + meant to help understand Git better, announced by its author Nic Hartley in + [Git Gud at git](https://dev.to/nichartley/git-gud-at-git-5d9k). + First mentioned in [Git Rev News Edition #48](https://git.github.io/rev_news/2019/02/27/edition-48/). + + [Git Gud](https://github.com/benthayer/git-gud), a command line game + designed to help you learn how to use the Git version control system. + Written in Python by Ben Thayer. First mentioned in + [Git Rev News Edition #72](https://git.github.io/rev_news/2021/02/27/edition-72/). + + [Oh My Git!](https://ohmygit.org/), an open source game about learning Git, + written using the Godot game engine ([source](https://github.com/git-learning-game/oh-my-git)). + There was a lightning talk about this game at FOSDEM 2021: + [Building a Git learning game: A playful approach to version control](https://fosdem.org/2021/schedule/event/git_learning_game/). + First mentioned in [Git Rev News Edition #72](https://git.github.io/rev_news/2021/02/27/edition-72/). + + [Git-Sim](https://github.com/initialcommit-com/git-sim) tool (written in Python) + to visually simulate Git operations in your own repos with a single terminal command. + Described in [Git-Sim: Visually Simulate Git Operations In Your Own Repos](https://initialcommit.com/blog/git-sim) + (mentioned in [Git Rev News Edition #95](https://git.github.io/rev_news/2023/01/31/edition-95/)) + and [Git-Sim 3 Month Dev Update: Community Response, New Features, & The Future](https://initialcommit.com/blog/git-sim-3-month-dev-update) + (mentioned in [Edition #98](https://git.github.io/rev_news/2023/04/30/edition-98/)). + + [Visualize Git](http://git-school.github.io/visualizing-git/) web app + that illustrates what's going on under the hood when you use common Git operations, + first mentioned in [Git Rev News Edition #107](https://git.github.io/rev_news/2024/01/31/edition-107/). + + [Devlands](https://devlands.com/), which is the game that creates + immersive experience to help learning Git. + First mentioned in [Git Rev News Edition #122](https://git.github.io/rev_news/2025/04/30/edition-122/). ++ [Ferriby](https://github.com/dawedawe/ferriby) is a CLI game + where you try to keep Ferrises alive and happy + by feeding them commits in your repositories. + Written in Rust, under MIT license. ++ [Pride Versioning](https://pridever.org/), + a [joking take](https://mastodon.online/@nikitonsky/113691789641950263) + on [Semantic Versioning (SemVer)](https://semver.org/). + ## Releases From 799029d5dbd07bfa84857d36109115b8192f1c64 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Nar=C4=99bski?= Date: Sat, 2 Aug 2025 02:24:23 +0200 Subject: [PATCH 22/45] rn-125: More info about git-phoenix tool --- rev_news/drafts/edition-125.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index d6111b479..4e61d6f55 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -471,7 +471,10 @@ __Git tools and sites__ a new file format specification for Extensible Diffs, fully backwards-compatible with existing tools, while also being future-proof and remaining human-readable. -- [git-phoenix](https://github.com/yaitskov/git-phoenix) does repository recovery. ++ [git-phoenix](https://github.com/yaitskov/git-phoenix) is a command line tool + that does repository recovery after accidental removal or file system failure, + using [photorec](https://www.cgsecurity.org/wiki/PhotoRec) (or similar tool). + Written in Haskell, under 3-clause BSD license. + [wtp (Worktree Plus)](https://github.com/satococoa/wtp) is a Git worktree management tool that extends git's worktree functionality with automated setup, branch tracking, and project-specific hooks. From 9d58ac6329d13bed06403a047a6d9cf3bb54289d Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sat, 2 Aug 2025 10:22:41 +0200 Subject: [PATCH 23/45] rn-125: add Usman Akinyemi among the helpers --- rev_news/drafts/edition-125.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index 98251ea42..f69da0cd0 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -641,5 +641,5 @@ Christian Couder <>, Jakub Narębski <>, Markus Jansen <> and Kaartic Sivaraam <> -with help from brian m. carlson, Aditya Garg, +with help from Usman Akinyemi, brian m. carlson, Aditya Garg, Erik-B. Ernst and Bruno Brito. From 6a22592df4b85e11e7bfef4b6038fe1545f5fb13 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sat, 2 Aug 2025 10:26:14 +0200 Subject: [PATCH 24/45] rn-125: tweak wording in main article --- rev_news/drafts/edition-125.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index f69da0cd0..93ab3a7d0 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -59,7 +59,7 @@ This edition covers what happened during the months of June and July 2025. changes to `git send-email`. He mentioned that he was sending the email series using the very patches he was proposing, via Outlook. - The first patch, which was a rebased version of + The first patch was a rebased version of [an earlier patch by Julian Swagemakers](https://lore.kernel.org/git/20250125190131.48717-1-julian@swagemakers.org/) adding support for OAuth2 authentication, which started to be required by Microsoft. Julian's patch unfortunately had been waiting From 00f1e58cedc8a4d59eef310ebd8de3f5ca8b48a1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= Date: Sat, 2 Aug 2025 10:36:36 +0200 Subject: [PATCH 25/45] rn-125: minor copy edit --- rev_news/drafts/edition-125.md | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index 93ab3a7d0..e03765cf2 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -232,7 +232,7 @@ welcome your thoughts and feedback!_ been moments when some of my contributions led to insights even long time contributors hadn’t considered, including Junio Hamano. That boosted my confidence not just in contributing to Git, but to other - software projects as well i.e I can get my patches accepted anywhere, + software projects as well, i.e., I can get my patches accepted anywhere, I just need to convince others that it actually solves a problem. * **How do you balance your contributions with other responsibilities @@ -271,7 +271,7 @@ welcome your thoughts and feedback!_ clear, structured commit messages. Git commits, like those in the Linux kernel, follow a thoughtful format: describe the current state, the problem, and the fix. From reading most of the commit messages in - Git, you would have understood and been to visualize what the changes + Git, you would have understood and been able to visualize what the changes will look like. It also makes it easy to track the changes to other prerequisite commits. I have been using the Git commit messages format in other projects and I really love it. @@ -394,11 +394,11 @@ __Various__ + [[LWN.net] A set of Git security-fix releases](https://lwn.net/Articles/1029182/) by Jonathan Corbet on LWN\.net, and
[Multiple vulnerabilities fixed in Git](https://www.openwall.com/lists/oss-security/2025/07/08/4) - by Taylor Blau on oss-security mailing list + by Taylor Blau on oss-security mailing list. + [[ANNOUNCE] Git v2.50.1 and friends](https://public-inbox.org/git/xmqqzfdevcov.fsf@gitster.g/t/#u) - by Junio C Hamano on the git mailing list. + by Junio C Hamano on the Git mailing list. + [Launchpad](https://launchpad.net/) is [phasing out Bazaar code hosting](https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189). - This post provides link to the [Migrate a Repository From Bazaar to Git](https://jugmac00.github.io/blog/migrate-a-repository-from-bazaar-to-git/) article. + This post provides a link to the [Migrate a Repository From Bazaar to Git](https://jugmac00.github.io/blog/migrate-a-repository-from-bazaar-to-git/) article. __Light reading__ @@ -450,7 +450,7 @@ __Light reading__ [Radicle](https://radicle.xyz/) is the distributed git hosting system, first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). + [Cutting GitHub out of the loop](https://www.circusscientist.com/2025/07/23/cutting-github-out-of-the-loop/) - (by deploying to VPS with Git and SSH). + (by deploying to a VPS with Git and SSH). Written by tomjuggler on The Circus Scientist Site. + [Super Easy* 2-Stage Git Deployment](https://ratfactor.com/cards/super-easy-2-stage-git-deployment) by Dave Gauer on Dave's Virtual Box of Cards. @@ -500,35 +500,35 @@ __Git tools and sites__ It helps keep your development environment settings organized, versioned, and synchronized across multiple machines and projects. DotProj uses Git commands (commit, push, pull, clone) making it intuitive for developers. - Written as Bash shell script, under MIT license. + Written as a Bash shell script, under MIT license. + [git-remote-sqlite](https://github.com/chrislloyd/git-remote-sqlite) is a [Git protocol helper](https://git-scm.com/docs/gitremote-helpers) that helps you store a Git repository in a SQLite database. Written in Zig, under MIT license. + [Backlog.md](https://backlog.md/) is a tool that turns any folder with a Git repo - into a self‑contained project board, powered by plain Markdown files - and a zero‑config CLI. Written in TypeScript, under MIT license. AI ready. + into a self-contained project board, powered by plain Markdown files + and a zero-config CLI. Written in TypeScript, under MIT license. AI ready. + [git-resolve.sh](https://elixir.bootlin.com/linux/v6.16-rc3/source/scripts/git-resolve.sh) is a Bash script that resolves a short git commit ID to its full SHA-1 hash, which is particularly useful for fixing references in commit messages. - Under GPL-2.0 license. + Under GPL-2.0 license. + [GitHub Trends](https://www.githubtrends.io/) is a service that - uses GitHub API to bring you insightful metrics on your contributions, + uses the GitHub API to bring you insightful metrics on your contributions, broken by repository and language. + [DeepWiki](https://deepwiki.com/): AI-generated docs for any repo. This service turns any public GitHub repo into up-to-date documentation you can talk to (see for example [DeepWiki: git/git](https://deepwiki.com/git/git). DeepWiki is the free public version of [Devin Wiki](https://docs.devin.ai/work-with-devin/devin-wiki) and [Devin Search](https://docs.devin.ai/work-with-devin/devin-search).
- There are a few silimar projects, like + There are a few similar projects, like [Open Source DeepWiki](https://github.com/AsyncFuncAI/deepwiki-open) and [OpenDeepWiki](https://github.com/AIDotNet/OpenDeepWiki). + [GitHub Repository Maintenance Agent](https://github.com/pamelafox/github-repo-maintainer-agent/) is an AI-powered agent for triaging failed [Dependabot](https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide) pull requests - across one GitHub repositories. The agent uses [Pydantic AI](https://ai.pydantic.dev/) + across one's GitHub repositories. The agent uses [Pydantic AI](https://ai.pydantic.dev/) for LLM-based decisions and the GitHub API for repository, PR, and issue management. Written in Python, under MIT license. -+ [tangled](https://tangled.sh/) is new social-enabled git collaboration platform - built on [AT Protocol](https://atproto.com/) (that powers the Bluesky social network). ++ [tangled](https://tangled.sh/) is a new social-enabled git collaboration platform + built on the [AT Protocol](https://atproto.com/) (that powers the Bluesky social network). Written in Go, under MIT license; note that it is in alpha stage of development.
Compare with: + [Radicle](https://radicle.xyz/), a peer-to-peer, local-first code collaboration stack built on Git @@ -556,7 +556,7 @@ __Git tools and sites__ Under GPLv3 license. + [GitBug: Git Learning Simulator](https://github.com/dvig14/gitbug) is a CLI app that teaches Git through hands-on bug fixing. - It uses a realistic merge conflict scenario with visual feedback at every step + It uses a realistic merge conflict scenario with visual feedback at every step. The goal of the app is to help you learn by doing, not just reading. Written in Python, under MIT license, in early stage (alpha).
Compare with: From 76efb2dec49b8953c5a665ec72fb3a7f0bdbc630 Mon Sep 17 00:00:00 2001 From: Markus Jansen Date: Sat, 2 Aug 2025 19:42:17 +0200 Subject: [PATCH 26/45] =?UTF-8?q?rn-125:=20added=20=C5=A0t=C4=9Bp=C3=A1n?= =?UTF-8?q?=20N=C4=9Bmec=20as=20contributor,=20plus=20one=20really=20tiny?= =?UTF-8?q?=20formatting=20fix?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- rev_news/drafts/edition-125.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rev_news/drafts/edition-125.md b/rev_news/drafts/edition-125.md index e03765cf2..063e936ee 100644 --- a/rev_news/drafts/edition-125.md +++ b/rev_news/drafts/edition-125.md @@ -405,7 +405,7 @@ __Light reading__ + [Artisanal Handcrafted Git Repositories](https://drew.silcock.dev/blog/artisanal-git/) by Drew Silcock on drew's dev blog. - This article talks about how to handmake your Git repositories without using git commands. + This article talks about how to handmake your Git repositories without using `git` commands. You might also learn a bit more about how Git works under the hood during the process. + [How to use git worktree effectively with Python projects](https://www.andreagrandi.it/posts/how-to-use-git-worktree-effectively-with-python-projects/) (with the help of a simple [git-add-worktree.sh](https://gist.github.com/andreagrandi/542b438bf0017d93aff2b640037e3ce1) Bash script) @@ -642,4 +642,4 @@ Jakub Narębski <>, Markus Jansen <> and Kaartic Sivaraam <> with help from Usman Akinyemi, brian m. carlson, Aditya Garg, -Erik-B. Ernst and Bruno Brito. +Erik-B. Ernst, Bruno Brito and Štěpán Němec. From 71a8189bb7c5da792813a0f72ac0964674694b3b Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sat, 2 Aug 2025 22:00:26 +0200 Subject: [PATCH 27/45] Publish rn-125 in _posts/ --- .../edition-125.md => _posts/2025-07-31-edition-125.markdown | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename rev_news/drafts/edition-125.md => _posts/2025-07-31-edition-125.markdown (100%) diff --git a/rev_news/drafts/edition-125.md b/_posts/2025-07-31-edition-125.markdown similarity index 100% rename from rev_news/drafts/edition-125.md rename to _posts/2025-07-31-edition-125.markdown From c7485c1c36b187525a80de691f279601ff94a6f5 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sat, 2 Aug 2025 22:00:27 +0200 Subject: [PATCH 28/45] Add draft for rn-126 --- rev_news/drafts/edition-126.md | 60 ++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 rev_news/drafts/edition-126.md diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md new file mode 100644 index 000000000..536b8c95f --- /dev/null +++ b/rev_news/drafts/edition-126.md @@ -0,0 +1,60 @@ +--- +title: Git Rev News Edition 126 (August 31st, 2025) +layout: default +date: 2025-08-31 12:06:51 +0100 +author: chriscool +categories: [news] +navbar: false +--- + +## Git Rev News: Edition 126 (August 31st, 2025) + +Welcome to the 126th edition of [Git Rev News](https://git.github.io/rev_news/rev_news/), +a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to +subscribe, see [the Git Rev News page](https://git.github.io/rev_news/rev_news/) on [git.github.io](http://git.github.io). + +This edition covers what happened during the months of July 2025 and August 2025. + +## Discussions + + + + + + + + + +## Other News + +__Various__ + + +__Light reading__ + + + +__Git tools and sites__ + + +## Releases + + +## Credits + +This edition of Git Rev News was curated by +Christian Couder <>, +Jakub Narębski <>, +Markus Jansen <> and +Kaartic Sivaraam <> +with help from XXX. From f14062a33ffde25c66a723bec3cdbd04dfe60d61 Mon Sep 17 00:00:00 2001 From: Kaartic Sivaraam Date: Sun, 31 Aug 2025 00:00:20 +0530 Subject: [PATCH 29/45] rn-126: include interview with Seyi Kuforiji --- rev_news/drafts/edition-126.md | 227 ++++++++++++++++++++++++++++++++- 1 file changed, 224 insertions(+), 3 deletions(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 536b8c95f..0f43c2686 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -29,9 +29,230 @@ This edition covers what happened during the months of July 2025 and August 2025 ### Support --> - +## Developer Spotlight: Seyi Kuforiji + +_Editor’s note: This edition features a retrospective interview with a +contributor who contributed to Git through a mentoring program. We hope +the reflections shared by the Outreachy contributor will provide an +insightful perspective that benefits the community. As always, we +welcome your thoughts and feedback!_ + +* **Who are you and what do you do?** + + My name is Seyi Kuforiji, and I’m an Outreachy alum who worked on + [modernizing Git’s unit testing platform](https://seyi-kuforiji-902b48.gitlab.io/posts/week-1-Introduce-yourself) + by converting its homegrown unit test framework to use [Clar](https://github.com/clar-test/clar). + I studied geography at the University of Lagos, but my curiosity + and passion for computers and software drove me to start learning + Python and Git immediately after graduating. + + Since then, I’ve enjoyed exploring different areas of IT, from + software engineering to data science and DevOps, because I genuinely + love learning and experimenting with new tools. I also earned a + certification in Health Data Science and Precision Medicine from + Stanford University, which reflects my commitment to leveraging + technology to improve lives. Participating in Outreachy through Git + demonstrated to me the impact of open-source collaboration, and it has + strengthened my passion for developing solutions that give back to the + community. + + Outside of work, I’m usually diving into something new. Right now, the + [Linux graphics stack](https://lwn.net/Articles/955376/) has caught my + attention, but when I decide to give my brain a break from tech, I play + chess or watch sports. + +* **How did you initially become interested in contributing to Git, + and what motivated you to choose it as your Outreachy project?** + + Git was one of the first tools I ever learned years ago. At first, I + didn’t really understand it; I only knew a few commands like + `git clone`, `git add .`, and `git commit -m ""`, and I was + living life with just those. I remember during my 12-month software + engineering bootcamp, I helped some of my colleagues with Git because + I had this so-called “prior knowledge” and for a while, I was treated + like a genius, at least until they caught up! + + So when I saw Git on the list of Outreachy projects, I knew right away + that this was where I needed to be: to deepen my understanding of the + tool and maybe level up from “genius” to something closer to expert + wizardry. These days, some say I’m a wizard, others say I’m a maestro, + but I’m just a humble guy who enjoys learning and sharing knowledge. + +* How do you feel your contribution has impacted the Git community + or the broader open source ecosystem? + + My contribution to Git, which was modernizing its homegrown unit + testing framework to use Clar, has helped improve Git’s testing + capabilities by making the tests more maintainable, easier to + understand, and easier to extend to cover more edge cases in the + future. Clar brings additional benefits such as clearer test + reporting, a more structured way to organize tests, and improved + readability, which makes the testing process more approachable for new + contributors. While this was primarily an internal-facing improvement, + I believe it plays an important role in maintaining the reliability of + Git’s functions and operations. A stronger testing framework makes it + easier for both new and experienced contributors to work with the + codebase confidently, which in turn strengthens Git for the millions + of people who rely on it every day. + +* **Is there any aspect of Git that you now see differently after + having contributed to it?** + + Like I said earlier, I started out only knowing a handful of Git + commands to do basic operations. My biggest takeaway since + contributing to Git has been discovering the full power of its + interactive rebase. I always saw rebase on cheat sheets but never + really experienced its capabilities until I worked more deeply with + Git. The best way I can describe it is that it feels like a time + machine: I make changes and commits, Git captures those states in + time, and with interactive rebase, I can go back, rewrite history, and + improve it as if it were the first time. + + I still find it so cool that in my text editor, I can see files I had + already deleted in later commits come back to life during a rebase. It + completely changed how I view Git, not just as a version control + system, but as a powerful storytelling tool for code. + +* **How do you balance your contributions with other responsibilities + like work or school?** + + I usually create a schedule with a clear timeframe dedicated to + working on the Git project. For example, during Outreachy, I set aside + specific blocks of time each day, treating it almost like a regular + job. This helped me stay consistent, avoid distractions, and make + steady progress. + + I’ve learned that balancing open-source contributions with other + responsibilities is all about structure and prioritization. By + planning my week ahead, I can make sure that my work, personal life, + and contributions don’t clash. Of course, I also try to stay flexible; + some weeks are more demanding than others, but having a framework + keeps me grounded and ensures I can keep giving my best to Git. + +* **Can you share how GSoC helped enhance your technical and + non-technical skills (like communication, project management, etc.)?** + + My C and low-level engineering skills have improved immensely through + this experience. I now feel much more confident working in a large and + complex codebase, and I’ve built the mindset to take on hard problems + without shying away. This confidence is what’s encouraging me to dive + deeper into the Linux kernel, where I’ve been learning and + experimenting with the graphics stack and GPU drivers. My knowledge of + Git itself has also grown significantly, particularly with the + interactive rebase functionality, which has completely changed how I + think about version control and history management. + + On the non-technical side, I grew a lot in communication and project + management. I learned how to break down tasks into smaller, achievable + goals, track progress against deadlines, and ask for help effectively + when I was stuck. Collaborating with mentors and the wider Git + community also taught me the importance of giving clear updates in + blog posts and writing thoughtful commit messages. + + Overall, the experience didn’t just make me a better programmer; it + made me more disciplined, collaborative, and confident in working on + real-world projects. + +* **What was your biggest takeaway or learning from Outreachy that + you now apply regularly in your work?** + + My biggest takeaway from Outreachy is the balance between + understanding deeply and taking action. My mentor encouraged me to not + just know how things work but also to dig into why they work. At the + same time, I learned that it’s easy to get stuck in the learning + phase, waiting until you feel "ready." During my first few weeks, I + hesitated too much. What really helped me was realizing that you don’t + need to know everything before you start; you just need enough to + begin, and the rest comes as you build and iterate. That shift has + stayed with me and is something I now apply regularly in my life. + +* **What was the biggest challenge you faced during your contributions + to Git, and how did you overcome it?** + + One of the biggest challenges I faced was understanding the Git + codebase. Git is a very large and complex project with many + interconnected parts, and even though my task was limited to the unit + testing section, I also needed to understand the underlying + functionality being tested. At first, it felt daunting, but I overcame + this by burning the midnight candle, digging deeper, and committing + myself to continuous learning. Bit by bit, things started to make + sense. What really helped was breaking down the complexity into + smaller pieces and focusing on one area at a time, while also asking + lots of questions and referring back to documentation. + +* **Have you thought about mentoring new GSoC / Outreachy students?** + +Yes, I hope to mentor future Outreachy interns if the opportunity arise. + +* **If you could get a team of expert developers to work full time on + something in Git for a full year, what would it be?** + + A first-class graphical interface officially maintained by the Git + project, for those who prefer using an app instead of the command + line. + +* **What upcoming features or changes in Git are you particularly + excited about?** + + I’ve been reading recent discussions on the Git mailing list about how + Git might evolve in the age of AI, particularly around enabling + integrations with AI agents. The idea of extending Git’s capabilities + so that AI tools can better understand, interact with, and even + automate certain workflows is quite exciting. For example, AI-assisted + code reviews, intelligent merge conflict resolution, or automated + repository maintenance could become more seamless if Git had + standardized ways for agents to plug into its internals. + +* **What is your favorite Git-related tool/library, outside of Git + itself?** + + GitHub and GitLab + +* **What is your toolbox for interacting with the mailing list and for + development of Git?** + + I mostly work from the command line. For sending contributions, I use + `git format-patch` and `git send-email`, since I’m more comfortable with + CLI tools. + +* **How do you envision your own involvement with Git or other open + source projects in the future?** + + I intend to remain active in the Git community for many years by + making steady contributions. At the moment, I’m still learning and + exploring the project to identify areas where I can improve and add + value. Over time, I hope to grow into a consistent contributor and + take on more responsibility within the project. + +* What is your advice for people who want to start Git development? + Where and how should they start? + + For anyone starting Git development, I’d recommend a few key + resources. The "[Hacking Git](https://git.github.io/Hacking-Git/)” + guide is definitely a go-to resource for understanding how the + project is structured and how to navigate the codebase. + The [MyFirstContribution](https://git-scm.com/docs/MyFirstContribution) + page is also very helpful for learning how to get started with making + changes. Beyond that, the general Git documentation is valuable for + building a solid foundation. Starting small, asking questions, and + getting familiar with these resources can make the process much + smoother. + +* **Would you recommend other students or contributors to participate in + the GSoC, Outreachy or other mentoring programs, working on Git? + Why? Do you have advice for them?** + + 100% yes. Programs like GSoC and Outreachy give you the unique + opportunity to learn directly from some of the smartest and most + experienced contributors in the Git community. Having a mentor to + guide you through real contributions accelerates your learning, helps + you build confidence and good practices early on. I’d absolutely + recommend it. My advice would be: come with curiosity, patience, and + the willingness to learn. Don’t worry if you don’t understand + everything at first. Ask questions, read the documentation, and engage + with the community. The mentorship and the experience you gain are + invaluable. + ## Other News From 9efb711d48ea53d8d8285084ee3a8f1633716f51 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sun, 31 Aug 2025 12:53:34 +0200 Subject: [PATCH 30/45] rn-126: add releases --- rev_news/drafts/edition-126.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 0f43c2686..1ad3b30c0 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -270,6 +270,28 @@ __Git tools and sites__ ## Releases ++ Git [2.51.0](https://lore.kernel.org/git/xmqqikikk1hr.fsf@gitster.g/), +[2.51.0-rc2](https://lore.kernel.org/git/xmqqh5ybcfwt.fsf@gitster.g/), +[2.51.0-rc1](https://lore.kernel.org/git/xmqqikizoybn.fsf@gitster.g/), +[2.51.0-rc0](https://lore.kernel.org/git/xmqqms8f5889.fsf@gitster.g/) ++ Git for Windows [v2.51.0(1)](https://github.com/git-for-windows/git/releases/tag/v2.51.0.windows.1) ++ GitHub Enterprise [3.17.5](https://docs.github.com/enterprise-server@3.17/admin/release-notes#3.17.5), +[3.16.8](https://docs.github.com/enterprise-server@3.16/admin/release-notes#3.16.8), +[3.15.12](https://docs.github.com/enterprise-server@3.15/admin/release-notes#3.15.12), +[3.14.17](https://docs.github.com/enterprise-server@3.14/admin/release-notes#3.14.17) ++ GitLab [18.3.1, 18.2.5, 18.1.5](https://about.gitlab.com/releases/2025/08/27/patch-release-gitlab-18-3-1-released/), +[18.3](https://about.gitlab.com/releases/2025/08/21/gitlab-18-3-released/), +[18.2.4](https://about.gitlab.com/releases/2025/08/18/gitlab-18-2-4-released/), +[17.11.7](https://about.gitlab.com/releases/2025/08/15/gitlab-17-11-7-released/), +[18.2.2, 18.1.4, 18.0.6](https://about.gitlab.com/releases/2025/08/13/patch-release-gitlab-18-2-2-released/) ++ Gerrit Code Review [3.10.8](https://www.gerritcodereview.com/3.10.html#3108), +[3.11.5](https://www.gerritcodereview.com/3.11.html#3115), +[3.12.2](https://www.gerritcodereview.com/3.12.html#3122) ++ GitKraken [11.3.0](https://help.gitkraken.com/gitkraken-client/current/) ++ Git Cola [4.14.0](https://github.com/git-cola/git-cola/releases/tag/v4.14.0) ++ GitButler [0.15.16](https://github.com/gitbutlerapp/gitbutler/releases/tag/release/0.15.16), +[0.15.15](https://github.com/gitbutlerapp/gitbutler/releases/tag/release/0.15.15) ++ Sublime Merge [Build 2112](https://www.sublimemerge.com/download) ## Credits From e4b4e713f2f590266243516ad2631b075dea4120 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Sun, 31 Aug 2025 17:30:55 +0200 Subject: [PATCH 31/45] rn-126: improve releases --- rev_news/drafts/edition-126.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 1ad3b30c0..7d64b7982 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -274,11 +274,10 @@ __Git tools and sites__ [2.51.0-rc2](https://lore.kernel.org/git/xmqqh5ybcfwt.fsf@gitster.g/), [2.51.0-rc1](https://lore.kernel.org/git/xmqqikizoybn.fsf@gitster.g/), [2.51.0-rc0](https://lore.kernel.org/git/xmqqms8f5889.fsf@gitster.g/) -+ Git for Windows [v2.51.0(1)](https://github.com/git-for-windows/git/releases/tag/v2.51.0.windows.1) -+ GitHub Enterprise [3.17.5](https://docs.github.com/enterprise-server@3.17/admin/release-notes#3.17.5), -[3.16.8](https://docs.github.com/enterprise-server@3.16/admin/release-notes#3.16.8), -[3.15.12](https://docs.github.com/enterprise-server@3.15/admin/release-notes#3.15.12), -[3.14.17](https://docs.github.com/enterprise-server@3.14/admin/release-notes#3.14.17) ++ Git for Windows [v2.51.0(1)](https://github.com/git-for-windows/git/releases/tag/v2.51.0.windows.1), +[v2.51.0-rc2(1)](https://github.com/git-for-windows/git/releases/tag/v2.51.0-rc2.windows.1), +[v2.51.0-rc1(1)](https://github.com/git-for-windows/git/releases/tag/v2.51.0-rc1.windows.1), +[v2.51.0-rc0(1)](https://github.com/git-for-windows/git/releases/tag/v2.51.0-rc0.windows.1) + GitLab [18.3.1, 18.2.5, 18.1.5](https://about.gitlab.com/releases/2025/08/27/patch-release-gitlab-18-3-1-released/), [18.3](https://about.gitlab.com/releases/2025/08/21/gitlab-18-3-released/), [18.2.4](https://about.gitlab.com/releases/2025/08/18/gitlab-18-2-4-released/), @@ -287,6 +286,10 @@ __Git tools and sites__ + Gerrit Code Review [3.10.8](https://www.gerritcodereview.com/3.10.html#3108), [3.11.5](https://www.gerritcodereview.com/3.11.html#3115), [3.12.2](https://www.gerritcodereview.com/3.12.html#3122) ++ GitHub Enterprise [3.17.5](https://docs.github.com/enterprise-server@3.17/admin/release-notes#3.17.5), +[3.16.8](https://docs.github.com/enterprise-server@3.16/admin/release-notes#3.16.8), +[3.15.12](https://docs.github.com/enterprise-server@3.15/admin/release-notes#3.15.12), +[3.14.17](https://docs.github.com/enterprise-server@3.14/admin/release-notes#3.14.17) + GitKraken [11.3.0](https://help.gitkraken.com/gitkraken-client/current/) + Git Cola [4.14.0](https://github.com/git-cola/git-cola/releases/tag/v4.14.0) + GitButler [0.15.16](https://github.com/gitbutlerapp/gitbutler/releases/tag/release/0.15.16), From 1861a7bab87a950cf711912af5aa1662b336f215 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Mon, 1 Sep 2025 00:16:31 +0200 Subject: [PATCH 32/45] rn-126: add pull.autostash article --- rev_news/drafts/edition-126.md | 79 +++++++++++++++++++++++++++++++++- 1 file changed, 77 insertions(+), 2 deletions(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 7d64b7982..c75868d18 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -25,9 +25,84 @@ This edition covers what happened during the months of July 2025 and August 2025 ### Reviews --> - + +* [[BUG] git pull ignores pull.autostash=true configuration when used with --git-dir and --work-tree flags on a bare repository](https://lore.kernel.org/git/010001980c1ee007-2797fc86-fdf3-46e9-bec9-f8da2c9ebb8d-000000@email.amazonses.com/) + + Bryan Lee posted a bug report about the `pull.autostash` + configuration variable being ignored in a repository used to manage + his dotfiles. + + He expected his unstaged changes to be automatically stashed before + a pull when that configuration variable is set to `true`. Instead, + the command failed with an error message telling him to "Please + commit or stash them". So he thought Git ignored the autostash + configuration completely due to the setup, which consisted of a bare + repository and a separate work tree accessed through the following + alias: + + `$ alias dot='git --git-dir=$HOME/.dotfiles/ --work-tree=$HOME'` + + Lidong Yan replied to Bryan admitting that he wasn't sure why the + autostash feature would be ignored when using the `--git-dir` and + `--work-tree` flags. He suggested setting `rebase.autostash` instead + of `pull.autostash` to `true` though. + + Bryan Lee thanked Lidong saying that `pull.autostash` is not a Git + configuration option and that `rebase.autostash` does work for + rebase operations. But he raised the issue that Git silently accepts + invalid configuration keys without any warning, which can cause + users to waste a lot of time debugging. + + Lidong replied with a suggestion to add a `git config verify` + subcommand. But Junio Hamano, the Git maintainer, chimed in + expressing doubts about such a command, as Git cannot distinguish + between a typo of a known variable and a legitimate custom variable + that a user or a third-party tool might be using. Lidong elaborated + that such a command could work by having Git maintain an internal + registry of all valid keys, which could also be extended by users + and tools for their own custom configurations. + + Johannes Sixt suggested that instead of building a complex + verification system, it would be easier to fix the origin of the + misconception that `pull.autostash` was the correct configuration. + + Junio replied to Johannes that having `git pull` pay attention to + `rebase.autostash` was at least a documentation failure, if not a + bug. He argued that users have different expectations for a + relatively safe local rebase compared to a pull from a remote, which + could be riskier. Also it didn't make sense for `git pull` to + respect `rebase.autostash` but not `merge.autostash`. + + Ben Knoble then chimed in with a counter-argument to Junio. He + reasoned that since a `git pull` that rebases is conceptually a + fetch followed by a rebase, it would be "far more inconsistent" if + it didn't honor the rebase configuration. Breaking that expectation + would be unnatural for users taught to think of pull in that + way. Following this logic, he also supported the idea that a merging + pull should respect `merge.autostash`. + + Then Junio wondered if introducing a new, dedicated `pull.autostash` + variable would be a good idea. But soon Lidong came up with + [a patch](https://lore.kernel.org/git/20250717030732.75106-1-yldhome2d2@gmail.com/) + to actually add this configuration variable. + + Eric Sunshine reviewed the patch and left a number of suggestions to + improve it in many ways. After some discussions with Lidong and + Junio, Lidong posted + [a version 2 of the patch](https://lore.kernel.org/git/20250720124334.12045-1-yldhome2d2@gmail.com/). + + This new version implemented a number of improvements based on the + discussion. Some tests were added. The logic was updated to fall + back to either `rebase.autostash` or `merge.autostash` depending on + whether the pull performed a rebase or a merge. The order of + precedence was also clarified: `pull.autostash` now overrode the + more general `rebase.autostash` and `merge.autostash` + settings. Finally, the documentation was updated with more precise + explanations. + + This feature was released recently as part of Git v2.51.0. ## Developer Spotlight: Seyi Kuforiji From f0f103675e1d1f00fd6296c31d7eadd1e131eec4 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Mon, 1 Sep 2025 00:29:36 +0200 Subject: [PATCH 33/45] rn-126: remove redundant year --- rev_news/drafts/edition-126.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index c75868d18..e997f3ad7 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -13,7 +13,7 @@ Welcome to the 126th edition of [Git Rev News](https://git.github.io/rev_news/re a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to subscribe, see [the Git Rev News page](https://git.github.io/rev_news/rev_news/) on [git.github.io](http://git.github.io). -This edition covers what happened during the months of July 2025 and August 2025. +This edition covers what happened during the months of July and August 2025. ## Discussions From 0b76af14e8ac4c39b2653be6072d0220096268d9 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Mon, 1 Sep 2025 00:30:43 +0200 Subject: [PATCH 34/45] rn-126: add Seyi Kuforiji among the helpers --- rev_news/drafts/edition-126.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index e997f3ad7..052f86154 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -378,4 +378,4 @@ Christian Couder <>, Jakub Narębski <>, Markus Jansen <> and Kaartic Sivaraam <> -with help from XXX. +with help from Seyi Kuforiji. From 6139aecb8cef735ecd68a2e0e9119c1cbf001287 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Nar=C4=99bski?= Date: Mon, 1 Sep 2025 02:44:59 +0200 Subject: [PATCH 35/45] rn-126: Add links to various news, articles, sites, and tools --- rev_news/drafts/edition-126.md | 248 +++++++++++++++++++++++++++++++++ 1 file changed, 248 insertions(+) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 052f86154..1399ba2f9 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -333,15 +333,263 @@ Yes, I hope to mentor future Outreachy interns if the opportunity arise. __Various__ ++ [What’s new in Git 2.51.0?](https://about.gitlab.com/blog/what-s-new-in-git-2-51-0/) + by Karthik Nayak on GitLab Blog. It describes performance optimizations + for `git push` and `git fetch` (most significant when using "reftable" + backend for references), further plans for Git 3.0 (which can be + found in the [BreakingChanges document](https://gitlab.com/gitlab-org/git/-/blob/master/Documentation/BreakingChanges.adoc)), semi-removal of `git whatchanged` + (still available with `--i-still-use-this` flag), and marking + `git switch` and `git restore` as no longer experimental, + adding a new `--start-after` flag for `git for-each-ref` (that can be + combined with the `--count` flag to support pagination), etc. ++ [Highlights from Git 2.51](https://github.blog/open-source/git/highlights-from-git-2-51/) + by Taylor Blau on GitHub Blog. It describes cruft-free multi-pack indexes + (which currently require setting a new `repack.MIDXMustContainCruft` config option), + smaller packs with "path walk" method of collecting objects when repacking + (which you can try out with the new `--path-walk` command-line option), + a variant of the internal stash representation that can be used for stash interchange + (with new `export` and `import` commands for `git stash`), etc. ++ [Xet is now the default storage option for new users and organizations](https://huggingface.co/changelog/xet-default-for-new-users) + at [Hugging Face](https://huggingface.co/), switching from [Git LFS](https://git-lfs.com/). + This includes moving existing repositories from LFS to Xet. + To get the most out of Xet storage [read the usage instructions in the Hub docs](https://huggingface.co/docs/hub/en/storage-backends#using-xet-storage). + Note that Xet remains backward compatible with legacy clients optimized for Git LFS. + + [XetHub](https://xethub.com/) was first mentioned in passing in + [Git Rev News #95](https://git.github.io/rev_news/2023/01/31/edition-95/), + and its [benchmark by XetHub against S3, DVC, and Git LFS](https://about.xethub.com/blog/benchmarking-the-modern-development-experience) + was mentioned in [Git Rev News Edition #113](https://git.github.io/rev_news/2024/07/31/edition-113/). + + Compare with [DagsHub launching Direct Data Access in 2022](https://dagshub.com/blog/launching-data-streaming-and-upload/). + [DagsHub](https://dagshub.com/) was first mentioned in + [Git Rev News Edition #72](https://git.github.io/rev_news/2021/02/27/edition-72/), + then in [#85](https://git.github.io/rev_news/2022/03/31/edition-85/), + [#96](https://git.github.io/rev_news/2023/02/28/edition-96/), + [#107](https://git.github.io/rev_news/2024/01/31/edition-107/), and + [#113](https://git.github.io/rev_news/2024/07/31/edition-113/). + __Light reading__ ++ [The future of large files in Git is Git](https://tylercipriani.com/blog/2025/08/15/git-lfs/) + by Tyler Cipriani on his blog. It describes how can one use + partial clone today (and large object promisors in the future, + which are work in progress), instead of using [Git LFS](https://git-lfs.com/) + or similar solutions like [git-annex](https://git-annex.branchable.com/) + (or no longer actively developed solutions like git-media and git-fat), + or [DVC](https://dvc.org/) (Data Version Control). ++ [Code Review Can Be Better](https://tigerbeetle.com/blog/2025-08-04-code-review-can-be-better/) + (than GitHub's default code review process) + by matklad (Alex Kladov) on the TigerBeetle blog.
+ Mentions their [`git-review`](https://github.com/tigerbeetle/tigerbeetle/pull/2732) + work-in-progress tool, and also + + [Fossil](https://fossil-scm.org/) version control system with built-in project management + (first mentioned in [Git Rev News Edition #11](https://git.github.io/rev_news/2016/01/13/edition-11/)), + + [NoteDb](https://gerrit-review.googlesource.com/Documentation/note-db.html) backend + for [Gerrit](https://www.gerritcodereview.com/) - which allows storing review state in Git, + (NoteDb was first mentioned in [Git Rev News Edition #40](https://git.github.io/rev_news/2018/06/20/edition-40/)), + + [git-bug](https://github.com/git-bug/git-bug) tool that uses git to store information about issues / bugs + (first mentioned in [Git Rev News Edition #43](https://git.github.io/rev_news/2018/09/19/edition-43/)), + + [git-appraise](https://github.com/google/git-appraise) tool that uses git to store information about reviews + (first mentioned in [Git Rev News Edition #11](https://git.github.io/rev_news/2016/01/13/edition-11/)), + + [prr](https://doc.dxuuu.xyz/prr/index.html) ('pull request review') tool that brings mailing list style code reviews to Github PRs + (mentioned in [Git Rev News Edition #90](https://git.github.io/rev_news/2022/08/31/edition-90/)), + + [git-pr](https://pr.pico.sh/) project that leverages git native features to replace the entire pull request workflow, + (mentioned in [Git Rev News Edition #113](https://git.github.io/rev_news/2024/07/31/edition-113/)), and + + [How Jane Street Does Code Review](https://www.janestreet.com/tech-talks/janestreet-code-review/) + article by Ian Henry on Jane Street Tech Talks site. ++ [Jujutsu + Radicle = ❤️](https://radicle.xyz/2025/08/14/jujutsu-with-radicle) + by fintohaps on Radicle Blog, describing how the author use Jujutsu in tandem with Radicle. + + [Jujutsu (`jj`)](https://jj-vcs.github.io/jj/) is a Git-compatibile version control system + written in Rust, and was first mentioned in + [Git Rev News Edition #85](https://git.github.io/rev_news/2022/03/31/edition-85/). + + [Radicle](https://radicle.xyz/), a peer-to-peer, local-first code collaboration stack built on Git, + was first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). ++ [introducing spindle](https://blog.tangled.sh/ci) by Anirudh & Akshay on Tangled blog; + spindle is Tangled’s new CI runner built atop Nix and AT Protocol. + + [Tangled.sh](https://blog.tangled.sh/intro) is a new social-enabled Git collaboration platform + build on top of AT Protocol (which is behind [BlueSky](https://bsky.app/) + microblogging federated social media service). + First mentioned in [the previous edition of Git Rev News](https://git.github.io/rev_news/2025/07/31/edition-125/). + + Compare [Using Radicle CI for Development](https://radicle.xyz/2025/07/23/using-radicle-ci-for-development) + article by Lars Wirzenius, also mentioned in [Git Rev News #125](https://git.github.io/rev_news/2025/07/31/edition-125/). + [Radicle](https://radicle.xyz/) is another distributed git hosting system, + first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). ++ [How we used Radicle with GitHub Actions](https://radicle.xyz/2025/05/30/radicle-with-github-actions): + Quick guide to trying Radicle without dropping GitHub or whatever CI you’re using. + Published by rudolfs (Rūdolfs Ošiņš) on Radicle Blog. ++ [Archive Legacy GitHub Repos with Subtree](https://dev.to/tonymet/archive-legacy-github-repos-with-subtree-1dj3) + by Tony Metzidis on DEV\.to, about how to use `git subtree` to consolidate + hundreds of legacy experimental repos into an archive, + preserving all of the commit history. ++ [I'll think twice before using Github Actions again](https://ninkovic.dev/blog/2025/think-twice-before-using-github-actions) + by Nemanja Ninković on their blog. ++ [Git without a forge](https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/git-no-forge/) + by Simon Tatham on his quasiblog, describing how to interact with a bare git repo, + and explaining why he personally does not use any of Git forges. ++ [How I Cleaned Up My Git History Like a Boss (a.k.a. Fixing Wrong Author Emails)](https://dev.to/emrahg/how-i-cleaned-up-my-git-history-like-a-boss-aka-fixing-wrong-author-emails-19lb) + by Emrah G. on DEV\.to. The solution uses (deprecated) `git filter-branch` tool; + the recommended replacement is [`git filter-repo`](https://github.com/newren/git-filter-repo). + Also, you can correct the _visible_ e-mail with the [`.mailmap`](https://git-scm.com/docs/gitmailmap) file + (changing what Git shows, without having to rewrite history). ++ [Revolutionizing Git Workflows: The MCP Git Commit Generator](https://www.bampouris.eu/blog/mcp-git-commit-generator/) + by Theoklitos Bampouris on his blog (and also [on DEV\.to](https://dev.to/theoklitosbam7/revolutionizing-git-workflows-the-mcp-git-commit-generator-530m)), + about using Agentic AI and LLM chatbot, + leveraging the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction). + The generated commit message will follow [Conventional Commits](https://www.conventionalcommits.org/) conventions.
+ Note: please read the proposed commit message before accepting it, + especially for more complex changes. While AI agents can take information + from changes and from an issue tracker, they cannot write whys of the change; + they cannot access your thoughts. + + [Git Rev News Edition #97](https://git.github.io/rev_news/2023/03/31/edition-97/) + lists a few other tools that use GPT-3 / ChatGPT Large Language Model (LLM) + to help write commit messages. ++ [Better git status](https://purpleidea.com/blog/2025/08/04/better-git-status/) + by James (@purpleidea) on his blog. He uses git alias which examines + the terminal width, and uses `git status --column=nodense` if terminal is wide enough. ++ [Some Pretty Cool Git Tools To Save Your Sanity](https://fev.al/posts/git-tools/) + by Charles Féval on his blog. + Mentions `git revise` for splitting pull requests (PRs), + and own `git backup`, `git reparent`, `git split`, `git move-branch`, and `git bookmark`. ++ [Using Git worktrees for development](https://blog.kulman.sk/git-worktree/) + by Igor Kulman on his blog. ++ [Curing A Case Of Git-UX](https://oppi.li/posts/curing_a_case_of_git-UX/) + by Akshay on their blog; describes how one can improve git worktree UX + with the help of [fzf](https://github.com/junegunn/fzf) + (or [skim](https://github.com/lotabout/skim) or [fzy](https://github.com/jhawthorn/fzy)), + and shell functions. + + See also [Improving shell workflows with fzf](https://seb.jambor.dev/posts/improving-shell-workflows-with-fzf/), + mentioned in [Git Rev News Edition #74](https://git.github.io/rev_news/2021/04/30/edition-74/). ++ [Making my GitHub heatmap widget](https://leanrada.com/notes/github-heatmap-widget/) + Lean Rada on their blog. The created tool scrapes an HTML partial, and reformats it, + but is constructed in such way that it could have consume JSON from GitHub API instead. ++ [TryHackMe - Git Happens](https://jacen.moe/blog/20250805-tryhackme-git-happens/) + by Jacen Sekai on his blog, about [Git Happens](https://tryhackme.com/room/githappens): + an easy-ranked box on [TryHackMe](https://tryhackme.com/), website for + hands-on cyber security training through real-world scenarios. ++ [The Ingredients of a Productive Monorepo](https://blog.swgillespie.me/posts/monorepo-ingredients/) + by Sean Gillespie on his misguided thoughts blog. + + You can find a definition of "monorepo" and a list of various tools on the [Monorepo.tools](https://monorepo.tools/) site, + which was first mentioned in [Git Rev News Edition #84](https://git.github.io/rev_news/2022/02/28/edition-84/). ++ [Git and jujutsu: in miniature](https://lottia.net/notes/0013-git-jujutsu-miniature.html) + by Charlotte (lottia) on her blog (2024). ++ [Git Interactive Rebase TODO Order is Wrong](https://salferrarello.com/git-interactive-rebase-order-is-wrong/) + by Sal Ferrarello on his blog (2019), stating a personal preference for stack-like order, + with latest commits appearing on the top.
+ The author even wrote a Vim plugin, + [Interactive Rebase Reverse Vim](https://github.com/salcode/vim-interactive-rebase-reverse), + to reverse the order of the commits in an interactive git rebase. ++ [Every line of code is always documented](https://mislav.net/2014/02/hidden-documentation/) + by Mislav Marohnić on his blog (2014). The article describes how to + extract information about code snippet from project history using `git blame`, + 'pickaxe' search with `git log -S`, and + [git-churn](https://github.com/garybernhardt/dotfiles/blob/f0c0ff92209e5aed4fa3ef6faf056eb9944a8f12/bin/git-churn) script, + and how to stay on the right side of history + (among others, to be able to use this technique effectively). + + __Git tools and sites__ ++ [WRKFLW](https://github.com/bahdotsh/wrkflw) is a command-line tool + for validating and executing GitHub Actions workflows locally, + without requiring a full GitHub environment. + It helps developers test their workflows directly on their machines + before pushing changes to GitHub. + Written in Rust, under MIT license. + + Compare with [Act](https://github.com/nektos/act) command line tool + to run your GitHub Actions locally, using the Docker Engine API. + Written in Go, under MIT license. + Mentioned in [Git Rev News Edition #113](https://git.github.io/rev_news/2024/07/31/edition-113/). ++ [Setup DVC Action](https://github.com/marketplace/actions/setup-dvc-data-version-control) + by Iterative is a JavaScript action that can be used as a step in GitHub Actions.
+ [DVC](https://dvc.org) (Data Version Control) was first mentioned + in [Git Rev News Edition #42](https://git.github.io/rev_news/2018/08/22/edition-42/), + and many times since (most recent in [Edition #116](https://git.github.io/rev_news/2024/10/31/edition-116/)). ++ [Lappverk](https://codeberg.org/natkr/lappverk/) is a tool for modifying other people's software. + It works by keeping a series of `.patch` files as its source of truth + (like [quilt](https://savannah.nongnu.org/projects/quilt)), + but using temporary Git repositories as an interface to modify the patches, + rather than implementing its own version control system from scratch. + Written in Rust, under Apache 2.0 License. + Started out as Patchable internal tool.
+ You might also be interested in reading the announcement blog post: + [Modifying Other People's Software]() + by Natalie Klestrup Röijezon (natkr) on natkr's ramblings. + + Compare [patchwork](http://jk.ozlabs.org/projects/patchwork/) - a web-based patch tracking system + designed to facilitate the contribution and management of contributions to an open-source project, + first mentioned in [Git Rev News Edition #20](https://git.github.io/rev_news/2016/10/19/edition-20/). + + Compare [Stacked Git (StGit)](https://stacked-git.github.io/), + an application for managing Git commits as a stack of patches, + first mentioned in [Git Rev News Edition #17](https://git.github.io/rev_news/2016/07/20/edition-17/). + + Compare [B4 Tools](https://github.com/mricon/b4), a helper utility + to work with patches made available via a [public-inbox](https://public-inbox.org/README.html) archive like [lore.kernel.org](https://lore.kernel.org/). + This tool is written to make it easier to participate in a patch-based workflows, + like those used in the Linux kernel development. + First mentioned in [Git Rev News Edition #61](https://git.github.io/rev_news/2020/03/25/edition-61/). ++ [GitGenius](https://selvaneyas.github.io/gitgenius) is a smart and simple CLI tool + that explains Git errors in plain English and helps you fix them quickly. + Written in Python, under MIT license. + + See also [thefuck](https://github.com/nvbn/thefuck), a command line application + which corrects your previous console command (for example Git command) + if you made an error (like typos in command name), and it _didn't_ do what you wanted; + the tool was first mentioned in [Git Rev News Edition #101](https://git.github.io/rev_news/2023/07/31/edition-101/). + + Compare the [Oh Shit, Git!?!](http://ohshitgit.com/) / [Dangit, Git!?!](https://dangitgit.com/) + website by Katie Sylor-Miller, + first mentioned in [Git Rev News Edition #19](https://git.github.io/rev_news/2016/09/14/edition-19/). ++ [GIT.WTF!?!](https://git.wtf/) is a website with articles in which you can + find solutions to your Git problems, + along with tips & tricks to improve your Git workflows. ++ [GITHUB2FORGEJO](https://github.com/PatNei/GITHUB2FORGEJO) + is a Bash script for migrating all repositories from a GitHub user account + to a specified Forgejo instance. It supports mirroring or one-time cloning + and includes a cleanup feature for removing repositories on Forgejo + that no longer exist on GitHub. + Under GPL 3.0 license.
+ Based on [GitHub2Forgejo](https://github.com/RGBCube/GitHub2Forgejo) + Nushell script, also under GPL 3.0 license. + + [Forgejo](https://forgejo.org/) is a self-hosted lightweight software forge, + which started as a “soft” fork of Gitea (itself a fork of Gogs), + and was first mentioned in passing in [Git Rev News Edition #103](https://git.github.io/rev_news/2023/09/30/edition-103/). ++ [git-revise](https://git-revise.readthedocs.io/) is a Git subcommand, and Python library + for efficiently updating, splitting, and rearranging commits. + Under MIT License.
+ The [Introducing git-revise](https://mystor.github.io/git-revise.html) + blog post was mentioned in [Git Rev News Edition #54](https://git.github.io/rev_news/2019/08/21/edition-54/). ++ [git-tools](https://github.com/cfe84/git-tools) is a set of additional Git commands + to help you make crazy stuff in a very unsafe way. + Includes `git backup`, `git move-branch`, `git reparent` (similar to `git rebase --onto`), + `git split`, `git bookmark`, `git newbranch`, and `git get`. + Written in Go, under GPL 2.0 license. ++ [git-fetch-file](https://github.com/andrewmcwattersandco/git-fetch-file) is a utility + for importing specific files from other Git repositories into your own project + while keeping a manifest (`.git-remote-files`) that remembers where they came from + and what commit they belong to. + Written in Python, under GPL 2.0 license. ++ [git-word-blame](https://framagit.org/mdamien/git-word-blame) + is a tool that shows word-by-word authors of a file, creating TSV and HTML files. + Written in Python, under GPL 3.0 license. + The README includes links to a few alternative tools in "See also" section. ++ [gguser](https://github.com/withshubh/gguser) is a CLI tool + to easily switch between different Git user profiles. + It simplifies managing multiple GitHub or GitLab accounts + by allowing users to switch between profiles effortlessly. + Written in JavaScript for Node.js (npm), under Apache 2.0 License. ++ [GitLabForm](https://gitlabform.github.io/gitlabform/) is a specialized configuration-as-code tool + for GitLab's application settings, groups, projects, and more, + using hierarchical configuration written in YAML. + Written in Python, under MIT license.
+ See [GitlabForm for Gitlab repository automation](https://www.mikestreety.co.uk/blog/gitlabform-for-gitlab-repository-automation/) + blog post by Mike Street on his blog. ++ [gmap](https://github.com/seeyebe/gmap) is a fast command-line tool + (with terminal interface) to explore Git activity - heatmaps, churn, authorship, and more. + It helps you understand your Git repository at a glance - not just what changed, + but when, how much, and by whom. + Written in Rust, under MIT license. ++ [Ayllu](https://ayllu-forge.org/) is a code forge optimized for single instance deployments. + It is still a work in progress. Written in Rust, under AGPL license. + ## Releases From c12bf52506a7fa30fc31ac41e855953e74455d49 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Nar=C4=99bski?= Date: Mon, 1 Sep 2025 02:51:29 +0200 Subject: [PATCH 36/45] rn-126: Add links to patch-hub and kw/kworkflow from @lucasoshiro --- rev_news/drafts/edition-126.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 1399ba2f9..4880ce846 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -528,6 +528,13 @@ __Git tools and sites__ This tool is written to make it easier to participate in a patch-based workflows, like those used in the Linux kernel development. First mentioned in [Git Rev News Edition #61](https://git.github.io/rev_news/2020/03/25/edition-61/). ++ [patch-hub](https://github.com/kworkflow/patch-hub/tree/unstable) is a TUI tool + that streamlines the interaction of Linux developers + with patches archived on [lore.kernel.org](https://lore.kernel.org/). + Written in Rust, under GPL 2.0 license.
+ It is a spin-off of [kw](https://github.com/kworkflow/kworkflow), + a tool for helping Linux kernel developers in everyday tasks + (which is written in shell, and is under GPL 2.0 license). + [GitGenius](https://selvaneyas.github.io/gitgenius) is a smart and simple CLI tool that explains Git errors in plain English and helps you fix them quickly. Written in Python, under MIT license. From 330f9abc3bbf00450c5821686106761d185efa33 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Nar=C4=99bski?= Date: Mon, 1 Sep 2025 02:54:23 +0200 Subject: [PATCH 37/45] rn-126: Add link to DiffMem from @lucasoshiro --- rev_news/drafts/edition-126.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 4880ce846..837fbace1 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -596,6 +596,13 @@ __Git tools and sites__ Written in Rust, under MIT license. + [Ayllu](https://ayllu-forge.org/) is a code forge optimized for single instance deployments. It is still a work in progress. Written in Rust, under AGPL license. ++ [DiffMem](https://github.com/Growth-Kinetics/DiffMem) is a lightweight, + git-based memory backend designed for AI agents and conversational systems. + It uses Markdown files for human-readable storage, + Git for tracking temporal evolution through differentials, + and an in-memory BM25 index for fast, explainable retrieval. + This project is a proof-of-concept (PoC). + Written in Python, no license (!). ## Releases From a741cdd3000b4ebe990d3b81f976ba1bce360c6a Mon Sep 17 00:00:00 2001 From: Kaartic Sivaraam Date: Mon, 1 Sep 2025 12:26:24 +0530 Subject: [PATCH 38/45] rn-126: fix some formatting issues in the interview --- rev_news/drafts/edition-126.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 837fbace1..22b71a6e1 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -153,8 +153,8 @@ welcome your thoughts and feedback!_ wizardry. These days, some say I’m a wizard, others say I’m a maestro, but I’m just a humble guy who enjoys learning and sharing knowledge. -* How do you feel your contribution has impacted the Git community - or the broader open source ecosystem? +* **How do you feel your contribution has impacted the Git community + or the broader open source ecosystem?** My contribution to Git, which was modernizing its homegrown unit testing framework to use Clar, has helped improve Git’s testing @@ -257,7 +257,7 @@ welcome your thoughts and feedback!_ * **Have you thought about mentoring new GSoC / Outreachy students?** -Yes, I hope to mentor future Outreachy interns if the opportunity arise. + Yes, I hope to mentor future Outreachy interns if the opportunity arise. * **If you could get a team of expert developers to work full time on something in Git for a full year, what would it be?** From 408a216d4428efeb77faf6390f3cca298b4f29b3 Mon Sep 17 00:00:00 2001 From: Markus Jansen Date: Tue, 2 Sep 2025 10:36:54 +0200 Subject: [PATCH 39/45] rn-126: Supplied some tiny fixes and rephrasings; merged MR #794. Please scrutinize. --- rev_news/drafts/edition-126.md | 91 ++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 44 deletions(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 22b71a6e1..ceada3313 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -28,7 +28,7 @@ This edition covers what happened during the months of July and August 2025. ### Support -* [[BUG] git pull ignores pull.autostash=true configuration when used with --git-dir and --work-tree flags on a bare repository](https://lore.kernel.org/git/010001980c1ee007-2797fc86-fdf3-46e9-bec9-f8da2c9ebb8d-000000@email.amazonses.com/) +* [[BUG] `git pull` ignores `pull.autostash=true` configuration when used with `--git-dir` and `--work-tree` flags on a bare repository](https://lore.kernel.org/git/010001980c1ee007-2797fc86-fdf3-46e9-bec9-f8da2c9ebb8d-000000@email.amazonses.com/) Bryan Lee posted a bug report about the `pull.autostash` configuration variable being ignored in a repository used to manage @@ -49,8 +49,8 @@ This edition covers what happened during the months of July and August 2025. `--work-tree` flags. He suggested setting `rebase.autostash` instead of `pull.autostash` to `true` though. - Bryan Lee thanked Lidong saying that `pull.autostash` is not a Git - configuration option and that `rebase.autostash` does work for + Bryan Lee thanked Lidong saying that `pull.autostash` was not a Git + configuration option and that `rebase.autostash` did work for rebase operations. But he raised the issue that Git silently accepts invalid configuration keys without any warning, which can cause users to waste a lot of time debugging. @@ -97,7 +97,7 @@ This edition covers what happened during the months of July and August 2025. discussion. Some tests were added. The logic was updated to fall back to either `rebase.autostash` or `merge.autostash` depending on whether the pull performed a rebase or a merge. The order of - precedence was also clarified: `pull.autostash` now overrode the + precedence was also clarified: `pull.autostash` now overrides the more general `rebase.autostash` and `merge.autostash` settings. Finally, the documentation was updated with more precise explanations. @@ -144,7 +144,7 @@ welcome your thoughts and feedback!_ `git clone`, `git add .`, and `git commit -m ""`, and I was living life with just those. I remember during my 12-month software engineering bootcamp, I helped some of my colleagues with Git because - I had this so-called “prior knowledge” and for a while, I was treated + I had this so-called “prior knowledge”, and for a while, I was treated like a genius, at least until they caught up! So when I saw Git on the list of Outreachy projects, I knew right away @@ -335,7 +335,7 @@ __Various__ + [What’s new in Git 2.51.0?](https://about.gitlab.com/blog/what-s-new-in-git-2-51-0/) by Karthik Nayak on GitLab Blog. It describes performance optimizations - for `git push` and `git fetch` (most significant when using "reftable" + for `git push` and `git fetch` (most significant when using the "reftable" backend for references), further plans for Git 3.0 (which can be found in the [BreakingChanges document](https://gitlab.com/gitlab-org/git/-/blob/master/Documentation/BreakingChanges.adoc)), semi-removal of `git whatchanged` (still available with `--i-still-use-this` flag), and marking @@ -345,7 +345,7 @@ __Various__ + [Highlights from Git 2.51](https://github.blog/open-source/git/highlights-from-git-2-51/) by Taylor Blau on GitHub Blog. It describes cruft-free multi-pack indexes (which currently require setting a new `repack.MIDXMustContainCruft` config option), - smaller packs with "path walk" method of collecting objects when repacking + smaller packs with a "path walk" method of collecting objects when repacking (which you can try out with the new `--path-walk` command-line option), a variant of the internal stash representation that can be used for stash interchange (with new `export` and `import` commands for `git stash`), etc. @@ -372,33 +372,33 @@ __Light reading__ + [The future of large files in Git is Git](https://tylercipriani.com/blog/2025/08/15/git-lfs/) by Tyler Cipriani on his blog. It describes how can one use partial clone today (and large object promisors in the future, - which are work in progress), instead of using [Git LFS](https://git-lfs.com/) + which are work in progress) instead of using [Git LFS](https://git-lfs.com/) or similar solutions like [git-annex](https://git-annex.branchable.com/) - (or no longer actively developed solutions like git-media and git-fat), + (or no longer actively developed solutions like git-media and git-fat) or [DVC](https://dvc.org/) (Data Version Control). + [Code Review Can Be Better](https://tigerbeetle.com/blog/2025-08-04-code-review-can-be-better/) (than GitHub's default code review process) by matklad (Alex Kladov) on the TigerBeetle blog.
Mentions their [`git-review`](https://github.com/tigerbeetle/tigerbeetle/pull/2732) - work-in-progress tool, and also + work-in-progress tool, and also the + [Fossil](https://fossil-scm.org/) version control system with built-in project management - (first mentioned in [Git Rev News Edition #11](https://git.github.io/rev_news/2016/01/13/edition-11/)), + (first mentioned in [Git Rev News Edition #11](https://git.github.io/rev_news/2016/01/13/edition-11/)), the + [NoteDb](https://gerrit-review.googlesource.com/Documentation/note-db.html) backend for [Gerrit](https://www.gerritcodereview.com/) - which allows storing review state in Git, - (NoteDb was first mentioned in [Git Rev News Edition #40](https://git.github.io/rev_news/2018/06/20/edition-40/)), - + [git-bug](https://github.com/git-bug/git-bug) tool that uses git to store information about issues / bugs - (first mentioned in [Git Rev News Edition #43](https://git.github.io/rev_news/2018/09/19/edition-43/)), - + [git-appraise](https://github.com/google/git-appraise) tool that uses git to store information about reviews - (first mentioned in [Git Rev News Edition #11](https://git.github.io/rev_news/2016/01/13/edition-11/)), - + [prr](https://doc.dxuuu.xyz/prr/index.html) ('pull request review') tool that brings mailing list style code reviews to Github PRs - (mentioned in [Git Rev News Edition #90](https://git.github.io/rev_news/2022/08/31/edition-90/)), - + [git-pr](https://pr.pico.sh/) project that leverages git native features to replace the entire pull request workflow, - (mentioned in [Git Rev News Edition #113](https://git.github.io/rev_news/2024/07/31/edition-113/)), and + (NoteDb was first mentioned in [Git Rev News Edition #40](https://git.github.io/rev_news/2018/06/20/edition-40/)), the + + [git-bug](https://github.com/git-bug/git-bug) tool that uses Git to store information about issues / bugs + (first mentioned in [Git Rev News Edition #43](https://git.github.io/rev_news/2018/09/19/edition-43/)), the + + [git-appraise](https://github.com/google/git-appraise) tool that uses Git to store information about reviews + (first mentioned in [Git Rev News Edition #11](https://git.github.io/rev_news/2016/01/13/edition-11/)), the + + [prr](https://doc.dxuuu.xyz/prr/index.html) ('pull request review') tool that brings mailing list style code reviews to GitHub PRs + (mentioned in [Git Rev News Edition #90](https://git.github.io/rev_news/2022/08/31/edition-90/)), the + + [git-pr](https://pr.pico.sh/) project that leverages Git native features to replace the entire pull request workflow, + (mentioned in [Git Rev News Edition #113](https://git.github.io/rev_news/2024/07/31/edition-113/)), and the + [How Jane Street Does Code Review](https://www.janestreet.com/tech-talks/janestreet-code-review/) article by Ian Henry on Jane Street Tech Talks site. + [Jujutsu + Radicle = ❤️](https://radicle.xyz/2025/08/14/jujutsu-with-radicle) - by fintohaps on Radicle Blog, describing how the author use Jujutsu in tandem with Radicle. - + [Jujutsu (`jj`)](https://jj-vcs.github.io/jj/) is a Git-compatibile version control system + by fintohaps on Radicle Blog, describing how the author uses Jujutsu in tandem with Radicle. + + [Jujutsu (`jj`)](https://jj-vcs.github.io/jj/) is a Git-compatible version control system written in Rust, and was first mentioned in [Git Rev News Edition #85](https://git.github.io/rev_news/2022/03/31/edition-85/). + [Radicle](https://radicle.xyz/), a peer-to-peer, local-first code collaboration stack built on Git, @@ -411,7 +411,7 @@ __Light reading__ First mentioned in [the previous edition of Git Rev News](https://git.github.io/rev_news/2025/07/31/edition-125/). + Compare [Using Radicle CI for Development](https://radicle.xyz/2025/07/23/using-radicle-ci-for-development) article by Lars Wirzenius, also mentioned in [Git Rev News #125](https://git.github.io/rev_news/2025/07/31/edition-125/). - [Radicle](https://radicle.xyz/) is another distributed git hosting system, + [Radicle](https://radicle.xyz/) is another distributed Git hosting system, first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). + [How we used Radicle with GitHub Actions](https://radicle.xyz/2025/05/30/radicle-with-github-actions): Quick guide to trying Radicle without dropping GitHub or whatever CI you’re using. @@ -423,16 +423,16 @@ __Light reading__ + [I'll think twice before using Github Actions again](https://ninkovic.dev/blog/2025/think-twice-before-using-github-actions) by Nemanja Ninković on their blog. + [Git without a forge](https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/git-no-forge/) - by Simon Tatham on his quasiblog, describing how to interact with a bare git repo, - and explaining why he personally does not use any of Git forges. + by Simon Tatham on his quasiblog, describing how to interact with a bare Git repo, + and explaining why he personally does not use any of the Git forges. + [How I Cleaned Up My Git History Like a Boss (a.k.a. Fixing Wrong Author Emails)](https://dev.to/emrahg/how-i-cleaned-up-my-git-history-like-a-boss-aka-fixing-wrong-author-emails-19lb) - by Emrah G. on DEV\.to. The solution uses (deprecated) `git filter-branch` tool; + by Emrah G. on DEV\.to. The solution uses the (deprecated) `git filter-branch` tool; the recommended replacement is [`git filter-repo`](https://github.com/newren/git-filter-repo). Also, you can correct the _visible_ e-mail with the [`.mailmap`](https://git-scm.com/docs/gitmailmap) file (changing what Git shows, without having to rewrite history). + [Revolutionizing Git Workflows: The MCP Git Commit Generator](https://www.bampouris.eu/blog/mcp-git-commit-generator/) by Theoklitos Bampouris on his blog (and also [on DEV\.to](https://dev.to/theoklitosbam7/revolutionizing-git-workflows-the-mcp-git-commit-generator-530m)), - about using Agentic AI and LLM chatbot, + about using Agentic AI and an LLM chatbot, leveraging the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction). The generated commit message will follow [Conventional Commits](https://www.conventionalcommits.org/) conventions.
Note: please read the proposed commit message before accepting it, @@ -440,15 +440,15 @@ __Light reading__ from changes and from an issue tracker, they cannot write whys of the change; they cannot access your thoughts. + [Git Rev News Edition #97](https://git.github.io/rev_news/2023/03/31/edition-97/) - lists a few other tools that use GPT-3 / ChatGPT Large Language Model (LLM) + lists a few other tools that use the GPT-3 / ChatGPT Large Language Model (LLM) to help write commit messages. + [Better git status](https://purpleidea.com/blog/2025/08/04/better-git-status/) - by James (@purpleidea) on his blog. He uses git alias which examines - the terminal width, and uses `git status --column=nodense` if terminal is wide enough. + by James (@purpleidea) on his blog. He uses `git alias` which examines + the terminal width, and then `git status --column=nodense` if the terminal is wide enough. + [Some Pretty Cool Git Tools To Save Your Sanity](https://fev.al/posts/git-tools/) by Charles Féval on his blog. Mentions `git revise` for splitting pull requests (PRs), - and own `git backup`, `git reparent`, `git split`, `git move-branch`, and `git bookmark`. + and own `git backup`, `git reparent`, `git split`, `git move-branch`, and `git bookmark` commands. + [Using Git worktrees for development](https://blog.kulman.sk/git-worktree/) by Igor Kulman on his blog. + [Curing A Case Of Git-UX](https://oppi.li/posts/curing_a_case_of_git-UX/) @@ -459,8 +459,8 @@ __Light reading__ + See also [Improving shell workflows with fzf](https://seb.jambor.dev/posts/improving-shell-workflows-with-fzf/), mentioned in [Git Rev News Edition #74](https://git.github.io/rev_news/2021/04/30/edition-74/). + [Making my GitHub heatmap widget](https://leanrada.com/notes/github-heatmap-widget/) - Lean Rada on their blog. The created tool scrapes an HTML partial, and reformats it, - but is constructed in such way that it could have consume JSON from GitHub API instead. + Lean Rada on their blog. The created tool scrapes an HTML input partially and reformats it, + but is constructed in such way that it could have consumed JSON from GitHub API instead. + [TryHackMe - Git Happens](https://jacen.moe/blog/20250805-tryhackme-git-happens/) by Jacen Sekai on his blog, about [Git Happens](https://tryhackme.com/room/githappens): an easy-ranked box on [TryHackMe](https://tryhackme.com/), website for @@ -469,6 +469,8 @@ __Light reading__ by Sean Gillespie on his misguided thoughts blog. + You can find a definition of "monorepo" and a list of various tools on the [Monorepo.tools](https://monorepo.tools/) site, which was first mentioned in [Git Rev News Edition #84](https://git.github.io/rev_news/2022/02/28/edition-84/). ++ [Git Branching Explained: Base, Topic, and Parent Branches](https://www.git-tower.com/blog/base-topic-parent-branches) + by Bruno Brito on Tower Blog. + [Git and jujutsu: in miniature](https://lottia.net/notes/0013-git-jujutsu-miniature.html) by Charlotte (lottia) on her blog (2024). + [Git Interactive Rebase TODO Order is Wrong](https://salferrarello.com/git-interactive-rebase-order-is-wrong/) @@ -476,11 +478,11 @@ __Light reading__ with latest commits appearing on the top.
The author even wrote a Vim plugin, [Interactive Rebase Reverse Vim](https://github.com/salcode/vim-interactive-rebase-reverse), - to reverse the order of the commits in an interactive git rebase. + to reverse the order of the commits in an interactive `git rebase`. + [Every line of code is always documented](https://mislav.net/2014/02/hidden-documentation/) by Mislav Marohnić on his blog (2014). The article describes how to extract information about code snippet from project history using `git blame`, - 'pickaxe' search with `git log -S`, and + 'pickaxe' search with `git log -S`, and a [git-churn](https://github.com/garybernhardt/dotfiles/blob/f0c0ff92209e5aed4fa3ef6faf056eb9944a8f12/bin/git-churn) script, and how to stay on the right side of history (among others, to be able to use this technique effectively). @@ -498,15 +500,15 @@ __Git tools and sites__ It helps developers test their workflows directly on their machines before pushing changes to GitHub. Written in Rust, under MIT license. - + Compare with [Act](https://github.com/nektos/act) command line tool + + Compare with the [Act](https://github.com/nektos/act) command line tool to run your GitHub Actions locally, using the Docker Engine API. Written in Go, under MIT license. Mentioned in [Git Rev News Edition #113](https://git.github.io/rev_news/2024/07/31/edition-113/). + [Setup DVC Action](https://github.com/marketplace/actions/setup-dvc-data-version-control) by Iterative is a JavaScript action that can be used as a step in GitHub Actions.
[DVC](https://dvc.org) (Data Version Control) was first mentioned - in [Git Rev News Edition #42](https://git.github.io/rev_news/2018/08/22/edition-42/), - and many times since (most recent in [Edition #116](https://git.github.io/rev_news/2024/10/31/edition-116/)). + in [Git Rev News Edition #42](https://git.github.io/rev_news/2018/08/22/edition-42/) + and many times since (most recently in [Edition #116](https://git.github.io/rev_news/2024/10/31/edition-116/)). + [Lappverk](https://codeberg.org/natkr/lappverk/) is a tool for modifying other people's software. It works by keeping a series of `.patch` files as its source of truth (like [quilt](https://savannah.nongnu.org/projects/quilt)), @@ -559,7 +561,7 @@ __Git tools and sites__ + [Forgejo](https://forgejo.org/) is a self-hosted lightweight software forge, which started as a “soft” fork of Gitea (itself a fork of Gogs), and was first mentioned in passing in [Git Rev News Edition #103](https://git.github.io/rev_news/2023/09/30/edition-103/). -+ [git-revise](https://git-revise.readthedocs.io/) is a Git subcommand, and Python library ++ [git-revise](https://git-revise.readthedocs.io/) is a Git subcommand and Python library for efficiently updating, splitting, and rearranging commits. Under MIT License.
The [Introducing git-revise](https://mystor.github.io/git-revise.html) @@ -570,7 +572,7 @@ __Git tools and sites__ `git split`, `git bookmark`, `git newbranch`, and `git get`. Written in Go, under GPL 2.0 license. + [git-fetch-file](https://github.com/andrewmcwattersandco/git-fetch-file) is a utility - for importing specific files from other Git repositories into your own project + for importing specific files from other Git repositories into your own project, while keeping a manifest (`.git-remote-files`) that remembers where they came from and what commit they belong to. Written in Python, under GPL 2.0 license. @@ -578,7 +580,7 @@ __Git tools and sites__ is a tool that shows word-by-word authors of a file, creating TSV and HTML files. Written in Python, under GPL 3.0 license. The README includes links to a few alternative tools in "See also" section. -+ [gguser](https://github.com/withshubh/gguser) is a CLI tool ++ [`gguser`](https://github.com/withshubh/gguser) is a CLI tool to easily switch between different Git user profiles. It simplifies managing multiple GitHub or GitLab accounts by allowing users to switch between profiles effortlessly. @@ -589,7 +591,7 @@ __Git tools and sites__ Written in Python, under MIT license.
See [GitlabForm for Gitlab repository automation](https://www.mikestreety.co.uk/blog/gitlabform-for-gitlab-repository-automation/) blog post by Mike Street on his blog. -+ [gmap](https://github.com/seeyebe/gmap) is a fast command-line tool ++ [`gmap`](https://github.com/seeyebe/gmap) is a fast command-line tool (with terminal interface) to explore Git activity - heatmaps, churn, authorship, and more. It helps you understand your Git repository at a glance - not just what changed, but when, how much, and by whom. @@ -597,7 +599,7 @@ __Git tools and sites__ + [Ayllu](https://ayllu-forge.org/) is a code forge optimized for single instance deployments. It is still a work in progress. Written in Rust, under AGPL license. + [DiffMem](https://github.com/Growth-Kinetics/DiffMem) is a lightweight, - git-based memory backend designed for AI agents and conversational systems. + Git-based memory backend designed for AI agents and conversational systems. It uses Markdown files for human-readable storage, Git for tracking temporal evolution through differentials, and an in-memory BM25 index for fast, explainable retrieval. @@ -632,6 +634,7 @@ __Git tools and sites__ + GitButler [0.15.16](https://github.com/gitbutlerapp/gitbutler/releases/tag/release/0.15.16), [0.15.15](https://github.com/gitbutlerapp/gitbutler/releases/tag/release/0.15.15) + Sublime Merge [Build 2112](https://www.sublimemerge.com/download) ++ Tower for Mac [14](https://www.git-tower.com/blog/tower-mac-14) ([YouTube video](https://youtu.be/WYhtxBAzOB0)) ## Credits @@ -640,4 +643,4 @@ Christian Couder <>, Jakub Narębski <>, Markus Jansen <> and Kaartic Sivaraam <> -with help from Seyi Kuforiji. +with help from Seyi Kuforiji and Bruno Brito. From 1d5998d5e11e0fedccf3694988efc58287653f56 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Tue, 2 Sep 2025 13:04:38 +0200 Subject: [PATCH 40/45] rn-126: add Kinetic Merge release --- rev_news/drafts/edition-126.md | 1 + 1 file changed, 1 insertion(+) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index ceada3313..09cf0511d 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -635,6 +635,7 @@ __Git tools and sites__ [0.15.15](https://github.com/gitbutlerapp/gitbutler/releases/tag/release/0.15.15) + Sublime Merge [Build 2112](https://www.sublimemerge.com/download) + Tower for Mac [14](https://www.git-tower.com/blog/tower-mac-14) ([YouTube video](https://youtu.be/WYhtxBAzOB0)) ++ Kinetic Merge [1.9.0](https://github.com/sageserpent-open/kineticMerge/releases/tag/v1.9.0) ## Credits From 5f621a6c02143035696c8089a301ff9fa8334c40 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= Date: Tue, 2 Sep 2025 13:32:03 +0200 Subject: [PATCH 41/45] rn-126: minor copy edit Two changes which might warrant explanation: 1. 'misguided thoughts' is the title of Sean Gillespie's blog, but its lowercase spelling gives opportunity for the sentence to be misunderstood as editorial commentary (unlikely, granted, but gives the reader unnecessary pause); another option I considered was adding quotes or linkification, but saying just "on his blog" seems perfectly sufficient and clear. 2. Add quotes around a part of the git-tools description to indicate that "help you make crazy stuff in a very unsafe way" is a direct quote of the tool author's description. Otherwise I feel that this, too, will give the reader pause, as it provides almost no information, in contrast with what we usually try to achieve with descriptions. --- rev_news/drafts/edition-126.md | 36 +++++++++++++++++----------------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index 09cf0511d..c2ffc0a79 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -257,7 +257,7 @@ welcome your thoughts and feedback!_ * **Have you thought about mentoring new GSoC / Outreachy students?** - Yes, I hope to mentor future Outreachy interns if the opportunity arise. + Yes, I hope to mentor future Outreachy interns if the opportunity arises. * **If you could get a team of expert developers to work full time on something in Git for a full year, what would it be?** @@ -281,7 +281,7 @@ welcome your thoughts and feedback!_ * **What is your favorite Git-related tool/library, outside of Git itself?** - GitHub and GitLab + GitHub and GitLab. * **What is your toolbox for interacting with the mailing list and for development of Git?** @@ -370,7 +370,7 @@ __Various__ __Light reading__ + [The future of large files in Git is Git](https://tylercipriani.com/blog/2025/08/15/git-lfs/) - by Tyler Cipriani on his blog. It describes how can one use + by Tyler Cipriani on his blog. It describes how one can use partial clone today (and large object promisors in the future, which are work in progress) instead of using [Git LFS](https://git-lfs.com/) or similar solutions like [git-annex](https://git-annex.branchable.com/) @@ -404,12 +404,12 @@ __Light reading__ + [Radicle](https://radicle.xyz/), a peer-to-peer, local-first code collaboration stack built on Git, was first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). + [introducing spindle](https://blog.tangled.sh/ci) by Anirudh & Akshay on Tangled blog; - spindle is Tangled’s new CI runner built atop Nix and AT Protocol. + spindle is Tangled’s new CI runner built atop Nix and the AT Protocol. + [Tangled.sh](https://blog.tangled.sh/intro) is a new social-enabled Git collaboration platform - build on top of AT Protocol (which is behind [BlueSky](https://bsky.app/) + built on top of the AT Protocol (which is behind [BlueSky](https://bsky.app/) microblogging federated social media service). First mentioned in [the previous edition of Git Rev News](https://git.github.io/rev_news/2025/07/31/edition-125/). - + Compare [Using Radicle CI for Development](https://radicle.xyz/2025/07/23/using-radicle-ci-for-development) + + Compare the [Using Radicle CI for Development](https://radicle.xyz/2025/07/23/using-radicle-ci-for-development) article by Lars Wirzenius, also mentioned in [Git Rev News #125](https://git.github.io/rev_news/2025/07/31/edition-125/). [Radicle](https://radicle.xyz/) is another distributed Git hosting system, first mentioned in [Git Rev News Edition #49](https://git.github.io/rev_news/2019/03/20/edition-49/). @@ -448,7 +448,7 @@ __Light reading__ + [Some Pretty Cool Git Tools To Save Your Sanity](https://fev.al/posts/git-tools/) by Charles Féval on his blog. Mentions `git revise` for splitting pull requests (PRs), - and own `git backup`, `git reparent`, `git split`, `git move-branch`, and `git bookmark` commands. + and custom `git backup`, `git reparent`, `git split`, `git move-branch`, and `git bookmark` commands. + [Using Git worktrees for development](https://blog.kulman.sk/git-worktree/) by Igor Kulman on his blog. + [Curing A Case Of Git-UX](https://oppi.li/posts/curing_a_case_of_git-UX/) @@ -458,15 +458,15 @@ __Light reading__ and shell functions. + See also [Improving shell workflows with fzf](https://seb.jambor.dev/posts/improving-shell-workflows-with-fzf/), mentioned in [Git Rev News Edition #74](https://git.github.io/rev_news/2021/04/30/edition-74/). -+ [Making my GitHub heatmap widget](https://leanrada.com/notes/github-heatmap-widget/) - Lean Rada on their blog. The created tool scrapes an HTML input partially and reformats it, - but is constructed in such way that it could have consumed JSON from GitHub API instead. ++ [Making my GitHub heatmap widget](https://leanrada.com/notes/github-heatmap-widget/) by + Lean Rada on their blog. The created tool partially scrapes and reformats HTML input, + but is constructed in such way that it could consume JSON from GitHub API instead. + [TryHackMe - Git Happens](https://jacen.moe/blog/20250805-tryhackme-git-happens/) by Jacen Sekai on his blog, about [Git Happens](https://tryhackme.com/room/githappens): an easy-ranked box on [TryHackMe](https://tryhackme.com/), website for hands-on cyber security training through real-world scenarios. + [The Ingredients of a Productive Monorepo](https://blog.swgillespie.me/posts/monorepo-ingredients/) - by Sean Gillespie on his misguided thoughts blog. + by Sean Gillespie on his blog. + You can find a definition of "monorepo" and a list of various tools on the [Monorepo.tools](https://monorepo.tools/) site, which was first mentioned in [Git Rev News Edition #84](https://git.github.io/rev_news/2022/02/28/edition-84/). + [Git Branching Explained: Base, Topic, and Parent Branches](https://www.git-tower.com/blog/base-topic-parent-branches) @@ -481,7 +481,7 @@ __Light reading__ to reverse the order of the commits in an interactive `git rebase`. + [Every line of code is always documented](https://mislav.net/2014/02/hidden-documentation/) by Mislav Marohnić on his blog (2014). The article describes how to - extract information about code snippet from project history using `git blame`, + extract information about a code snippet from project history using `git blame`, 'pickaxe' search with `git log -S`, and a [git-churn](https://github.com/garybernhardt/dotfiles/blob/f0c0ff92209e5aed4fa3ef6faf056eb9944a8f12/bin/git-churn) script, and how to stay on the right side of history @@ -517,17 +517,17 @@ __Git tools and sites__ Written in Rust, under Apache 2.0 License. Started out as Patchable internal tool.
You might also be interested in reading the announcement blog post: - [Modifying Other People's Software]() + [Modifying Other People's Software](https://natkr.com/2025-08-14-modifying-other-peoples-software/) by Natalie Klestrup Röijezon (natkr) on natkr's ramblings. + Compare [patchwork](http://jk.ozlabs.org/projects/patchwork/) - a web-based patch tracking system - designed to facilitate the contribution and management of contributions to an open-source project, + designed to facilitate contribution and management of contributions to an open-source project, first mentioned in [Git Rev News Edition #20](https://git.github.io/rev_news/2016/10/19/edition-20/). + Compare [Stacked Git (StGit)](https://stacked-git.github.io/), an application for managing Git commits as a stack of patches, first mentioned in [Git Rev News Edition #17](https://git.github.io/rev_news/2016/07/20/edition-17/). + Compare [B4 Tools](https://github.com/mricon/b4), a helper utility to work with patches made available via a [public-inbox](https://public-inbox.org/README.html) archive like [lore.kernel.org](https://lore.kernel.org/). - This tool is written to make it easier to participate in a patch-based workflows, + This tool is written to make it easier to participate in patch-based workflows, like those used in the Linux kernel development. First mentioned in [Git Rev News Edition #61](https://git.github.io/rev_news/2020/03/25/edition-61/). + [patch-hub](https://github.com/kworkflow/patch-hub/tree/unstable) is a TUI tool @@ -567,7 +567,7 @@ __Git tools and sites__ The [Introducing git-revise](https://mystor.github.io/git-revise.html) blog post was mentioned in [Git Rev News Edition #54](https://git.github.io/rev_news/2019/08/21/edition-54/). + [git-tools](https://github.com/cfe84/git-tools) is a set of additional Git commands - to help you make crazy stuff in a very unsafe way. + to "help you make crazy stuff in a very unsafe way". Includes `git backup`, `git move-branch`, `git reparent` (similar to `git rebase --onto`), `git split`, `git bookmark`, `git newbranch`, and `git get`. Written in Go, under GPL 2.0 license. @@ -579,7 +579,7 @@ __Git tools and sites__ + [git-word-blame](https://framagit.org/mdamien/git-word-blame) is a tool that shows word-by-word authors of a file, creating TSV and HTML files. Written in Python, under GPL 3.0 license. - The README includes links to a few alternative tools in "See also" section. + The README includes links to a few alternative tools in the "See also" section. + [`gguser`](https://github.com/withshubh/gguser) is a CLI tool to easily switch between different Git user profiles. It simplifies managing multiple GitHub or GitLab accounts @@ -589,7 +589,7 @@ __Git tools and sites__ for GitLab's application settings, groups, projects, and more, using hierarchical configuration written in YAML. Written in Python, under MIT license.
- See [GitlabForm for Gitlab repository automation](https://www.mikestreety.co.uk/blog/gitlabform-for-gitlab-repository-automation/) + See the [GitlabForm for Gitlab repository automation](https://www.mikestreety.co.uk/blog/gitlabform-for-gitlab-repository-automation/) blog post by Mike Street on his blog. + [`gmap`](https://github.com/seeyebe/gmap) is a fast command-line tool (with terminal interface) to explore Git activity - heatmaps, churn, authorship, and more. From 80db241f220a0e72cc48b1954c85de2cc04b66f1 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Tue, 2 Sep 2025 18:07:24 +0200 Subject: [PATCH 42/45] =?UTF-8?q?rn-126:=20add=20=C5=A0t=C4=9Bp=C3=A1n=20N?= =?UTF-8?q?=C4=9Bmec=20among=20the=20helpers?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- rev_news/drafts/edition-126.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index c2ffc0a79..bb561035f 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -644,4 +644,4 @@ Christian Couder <>, Jakub Narębski <>, Markus Jansen <> and Kaartic Sivaraam <> -with help from Seyi Kuforiji and Bruno Brito. +with help from Štěpán Němec, Seyi Kuforiji and Bruno Brito. From 45d00d6fb9494e79680e6b2f1324ce2aba35d0ad Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Tue, 2 Sep 2025 18:09:00 +0200 Subject: [PATCH 43/45] rn-126: add Gerard Murphy among the helpers --- rev_news/drafts/edition-126.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rev_news/drafts/edition-126.md b/rev_news/drafts/edition-126.md index bb561035f..2645376d9 100644 --- a/rev_news/drafts/edition-126.md +++ b/rev_news/drafts/edition-126.md @@ -644,4 +644,5 @@ Christian Couder <>, Jakub Narębski <>, Markus Jansen <> and Kaartic Sivaraam <> -with help from Štěpán Němec, Seyi Kuforiji and Bruno Brito. +with help from Štěpán Němec, Gerard Murphy, +Seyi Kuforiji and Bruno Brito. From 5a617769ef4582e27f57ec335392e9838e2a3a3e Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Tue, 2 Sep 2025 21:08:44 +0200 Subject: [PATCH 44/45] Publish rn-126 in _posts/ --- .../edition-126.md => _posts/2025-08-31-edition-126.markdown | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename rev_news/drafts/edition-126.md => _posts/2025-08-31-edition-126.markdown (100%) diff --git a/rev_news/drafts/edition-126.md b/_posts/2025-08-31-edition-126.markdown similarity index 100% rename from rev_news/drafts/edition-126.md rename to _posts/2025-08-31-edition-126.markdown From b023148274cb4dbd06a82cf5c53bb7aa0a0b6c83 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Tue, 2 Sep 2025 21:08:44 +0200 Subject: [PATCH 45/45] Add draft for rn-127 --- rev_news/drafts/edition-127.md | 60 ++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 rev_news/drafts/edition-127.md diff --git a/rev_news/drafts/edition-127.md b/rev_news/drafts/edition-127.md new file mode 100644 index 000000000..c4615b51b --- /dev/null +++ b/rev_news/drafts/edition-127.md @@ -0,0 +1,60 @@ +--- +title: Git Rev News Edition 127 (September 30th, 2025) +layout: default +date: 2025-09-30 12:06:51 +0100 +author: chriscool +categories: [news] +navbar: false +--- + +## Git Rev News: Edition 127 (September 30th, 2025) + +Welcome to the 127th edition of [Git Rev News](https://git.github.io/rev_news/rev_news/), +a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to +subscribe, see [the Git Rev News page](https://git.github.io/rev_news/rev_news/) on [git.github.io](http://git.github.io). + +This edition covers what happened during the months of August and September 2025. + +## Discussions + + + + + + + + + +## Other News + +__Various__ + + +__Light reading__ + + + +__Git tools and sites__ + + +## Releases + + +## Credits + +This edition of Git Rev News was curated by +Christian Couder <>, +Jakub Narębski <>, +Markus Jansen <> and +Kaartic Sivaraam <> +with help from XXX.