Re: [PATCH 0/2] Fix misaligned output of git repo structure
- From
Jiang Xin <worldhello.net@gmail.com>
- Date
- Nov 15, 2025, 12:25 UTC
- Message-ID
- <CANYiYbGqLyZ9zvhR73z91yo2Yk-tT1LVcP--uEdaKL1hHJOEHA@mail.gmail.com>
- In-Reply-To
- <xmqqecq0ifld.fsf@gitster.g>
On Sat, Nov 15, 2025 at 3:22 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 27 quoted lines
> > Jiang Xin <worldhello.net@gmail.com> writes: > > >> Is `Co-developed-by` supposed to have a different meaning than the more > >> common `Co-authored-by`? > > > > This is a very good question. > > > > **Background** > > > > At Alibaba Cloud, our development team uses a variety of AI coding tools, > > including Cursor, Claude Code, Gemini-CLI, Lingma, and Qoder, etc. To > > measure adoption—specifically, how many developers are using AI coding > > tools and how much code is AI-generated—we needed a unified tracking > > mechanism compatible with all these tools. I chose to implement a git > > commit-msg hook that automatically detects the AI coding tool responsible > > for a commit based on environment variables at commit time. > > In other words, addition of this is solely to help corporations like > Alibaba to measure which AI tools are used (and what correlation > there are between success rate of the patches and the tools that > generated them, etc.. > > What is in it for us? What benefit are we getting in exchange for > tolerating these additional trailer lines in our log messages? > > A few random thoughts about generated contents:
Regardless of whether the trailer used in commits to identify AI coding tools was leaked intentionally or unintentionally, the following insights are extremely valuable—thank you!
I’ll add the appropriate configuration to disable the commit-msg hook’s automatic modification of commit messages for git.git repositories, and I’ll review any AI-generated code more carefully, if present.
-- Jiang Xin