Skip to content

feat: add a note on llm trailer in commit message - #2504

Open
CommanderStorm wants to merge 1 commit into
rust-lang:mainfrom
CommanderStorm:add-note-on-llm-trailer
Open

CommanderStorm wants to merge 1 commit into
rust-lang:mainfrom
CommanderStorm:add-note-on-llm-trailer

Conversation

@CommanderStorm

@CommanderStorm CommanderStorm commented Sep 13, 2026

Copy link
Copy Markdown

#triagebot > Scanning for LLM trailers

Should be pretty much what we want, or? 🤔
Not sure of the exact wording, that stuff is hard project wide..

LLM usage

I asked claude for the list of semi-popular LLM_CO_AUTHORS, since I only know noreply@antropic.com...
I have no data to back this up, but LGTM 🤷🏻

I also asked for these session things that linux and claude use, since the first is something that people MIGHT use and the second something that they might forget to delete :)
Apparently, that is not really a thing for others, also no data to back this up

@CommanderStorm CommanderStorm changed the title feat: add a note on llm trailer feat: add a note on llm trailer in commit message Sep 13, 2026
Comment on lines +15 to +24
/// `Co-authored-by` values identifying an LLM agent.
/// Matched on the email, as "Claude" could possibly be a human name.
const LLM_CO_AUTHORS: &[&str] = &[
"noreply@anthropic.com",
"copilot@users.noreply.github.com",
"cursoragent@cursor.com",
"@aider.chat",
"devin-ai-integration[bot]",
"google-labs-jules[bot]",
];

@Urgau Urgau Sep 14, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is exactly what I afraid in Zulip. I don't want us to maintain such an ever growing list.

I would fine if someone else, outside this repository, even outside this org, maintained this list, but not triagebot.

View changes since the review

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To clarify what the prefered solution is:

  • make it configurable, maybe with this default
  • move it to two git gists which I maintain

@rustbot

This comment has been minimized.

@rustbot

rustbot commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants