[TSC]: Whitelist claude bot in our cla

[evenstensberg]

Have you used AI?

No

Description

easycla still fails on "@claude"

[evenstensberg]

@bensternthal can you help us with this?

[bensternthal]

@evenstensberg yep happy to help, can you link to an example PR.

[evenstensberg]

CC @alexander-akait

[alexander-akait]

webpack/enhanced-resolve#525 example

@bensternthal

[bensternthal]

@alexander-akait & @evenstensberg Can you check if this commit was co-signed. It does not appear to be but I might be wrong. With easycla, commits have to be co signed, see below from a previous issue. If this was co-signed let me know and I will file a ticket:

To address this, we've also enabled a feature that checks the co-author's information. This is a requirement to ensure the real author—the co-author—has a valid EasyCLA signature with the project. The caveat is that this check will also affect normal pull requests that use the co-author field. These pull requests must adhere to the following standards:

• By ID: If the co-author line is formatted as Co-authored-by: Some Name <id+login@users.noreply.github.com>, EasyCLA will use the numeric ID to find the co-author via the GitHub API.
• By Login: If the line is Co-authored-by: Some Name <login@users.noreply.github.com>, EasyCLA will use the login as the GitHub username.
• By Email: If the line is Co-authored-by: Some Name email@domain, EasyCLA will attempt to find the co-author by their email address. Note that the email must be public on the GitHub profile.
• Fallback: If no user is found within GitHub, EasyCLA will lookup its own users table to find a signature. If there is a previous acknowledgement or signature for the contributor, EasyCLA check will pass. If there is not a previous acknowledgement or signature for the contributor, the check will fail.

[evenstensberg]

@alexander-akait we cant approve only claude commits we need a github author to co-sign each commit.

[alexander-akait]

We really need to support the agents instruction file which supports has org's wide, but it is on GitHub side