By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc amazing tip
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc Does anyone know if this is triggered by Clod opening a PR or Issue, or is it actual merged commits?
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc Signed in specifically to do this. Thanks.
-
@mcc Does anyone know if this is triggered by Clod opening a PR or Issue, or is it actual merged commits?
@Taffer merged commits seems to be the only possibility that makes sense, but Microsoft is very mysterious?
-
@mcc Does anyone know if this is triggered by Clod opening a PR or Issue, or is it actual merged commits?
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc made a mastodon account to tell you this fucking rules, thank you
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc Consider the following as well:
https://github.com/cursoragent
https://github.com/gemini-code-assistCopilot doesn't let you block it unfortunately.
-
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc works pretty well. I have done an obvious test


-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc thank you for the suggestion, this has proven to be a real engine for interpersonal disappointment
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc oh no -
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc interesting. Iβm not sure about the sensitivity of this as a marker; when I go to a repository I use a lot, I donβt see this banner, but I do see a recently edited folder called .claude β am I misunderstanding when I assume that means some of the code has been written by this tool?
-
@mcc interesting. Iβm not sure about the sensitivity of this as a marker; when I go to a repository I use a lot, I donβt see this banner, but I do see a recently edited folder called .claude β am I misunderstanding when I assume that means some of the code has been written by this tool?
@emjonaitis The marker appears whenever a git commit is created with the "co-authored-by" label. This is something claude can be configured to not create:
Moreover, one assumes that this only occurs when claude actually *performs the commit*. I would assume there are means of using claude where claude changes the code on disk and then the co-authored-by does not appear. Unfortunately, I don't know how to get an answer to that question without talking to a claude user
-
@emjonaitis The marker appears whenever a git commit is created with the "co-authored-by" label. This is something claude can be configured to not create:
Moreover, one assumes that this only occurs when claude actually *performs the commit*. I would assume there are means of using claude where claude changes the code on disk and then the co-authored-by does not appear. Unfortunately, I don't know how to get an answer to that question without talking to a claude user
@emjonaitis The .claude directory is, *as far as I know* (again, this is partially assumptions) configuration for claude to help it work with the codebase. Anyone who adds such a directory is essentially *inviting* claude commits. However technically they might not be using it to create code, they technically could be using it to answer questions about the codebase. Technically. One assumes this results in as much global warming as using it to write code however.
-
@emjonaitis The .claude directory is, *as far as I know* (again, this is partially assumptions) configuration for claude to help it work with the codebase. Anyone who adds such a directory is essentially *inviting* claude commits. However technically they might not be using it to create code, they technically could be using it to answer questions about the codebase. Technically. One assumes this results in as much global warming as using it to write code however.
@mcc @emjonaitis For context this flags people using agentic coding, i.e., having Claude code running on your machine, actively going through your folders and making changes. If they allow Claude to commit, it will do so under its own name unless disabled. This is the same with Cursor and Gemini.
The .claude folder in repos means they're using Claude to write the code; it's a per-project config file for the tool. It's similar to a .cursor file; it means it was used to write the code and is a better indicator than the co-authored commit.
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
@mcc Holly...

-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
Additional notes (1 of 3)
mcc (@mcc@mastodon.social)
@emjonaitis@mathstodon.xyz The marker appears whenever a git commit is created with the "co-authored-by" label. This is something claude can be configured to not create: https://code.claude.com/docs/en/settings#:~:text=Claude%20Code%22%2C%20%22pr%22%3A%20%22%22%7D-,includecoauthoredby,-Deprecated%3A%20Use%20attribution Moreover, one assumes that this only occurs when claude actually *performs the commit*. I would assume there are means of using claude where claude changes the code on disk and then the co-authored-by does not appear. Unfortunately, I don't know how to get an answer to that question without talking to a claude user
Mastodon (mastodon.social)
-
Additional notes (1 of 3)
mcc (@mcc@mastodon.social)
@emjonaitis@mathstodon.xyz The marker appears whenever a git commit is created with the "co-authored-by" label. This is something claude can be configured to not create: https://code.claude.com/docs/en/settings#:~:text=Claude%20Code%22%2C%20%22pr%22%3A%20%22%22%7D-,includecoauthoredby,-Deprecated%3A%20Use%20attribution Moreover, one assumes that this only occurs when claude actually *performs the commit*. I would assume there are means of using claude where claude changes the code on disk and then the co-authored-by does not appear. Unfortunately, I don't know how to get an answer to that question without talking to a claude user
Mastodon (mastodon.social)
Additional notes (2 of 3)
Sparrow (@kstrlworks@techhub.social)
@mcc@mastodon.social @emjonaitis@mathstodon.xyz For context this flags people using agentic coding, i.e., having Claude code running on your machine, actively going through your folders and making changes. If they allow Claude to commit, it will do so under its own name unless disabled. This is the same with Cursor and Gemini. The .claude folder in repos means they're using Claude to write the code; it's a per-project config file for the tool. It's similar to a .cursor file; it means it was used to write the code and is a better indicator than the co-authored commit.
TechHub (techhub.social)
-
Additional notes (2 of 3)
Sparrow (@kstrlworks@techhub.social)
@mcc@mastodon.social @emjonaitis@mathstodon.xyz For context this flags people using agentic coding, i.e., having Claude code running on your machine, actively going through your folders and making changes. If they allow Claude to commit, it will do so under its own name unless disabled. This is the same with Cursor and Gemini. The .claude folder in repos means they're using Claude to write the code; it's a per-project config file for the tool. It's similar to a .cursor file; it means it was used to write the code and is a better indicator than the co-authored commit.
TechHub (techhub.social)
Additional notes (3 of 3)
Sparrow (@kstrlworks@techhub.social)
@mcc@mastodon.social Consider the following as well: https://github.com/cursoragent https://github.com/gemini-code-assist Copilot doesn't let you block it unfortunately.
TechHub (techhub.social)