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
oh, that's interesting & useful. thank you!
@CoralineAda @mcc Thank you so much for this, Coraline - you may have just saved humanity!
Hmmm. Perhaps we could use the GH API to give us an early warning when a much loved codebase is compromised. Maybe starting with something like this:
curl -s -H "Authorization: Bearer $AUTH_TOKEN" \
-H "Accept: application/vnd.github+json" \
"https://api.github.com/search/issues?q=is:pr+is:merged+author:claude&per_page=100&page=1" \
| jq -r '.items[].repository_url | sub("https://api.github.com/repos/";"")' \
| sort \
| uniq -c
This gets us a very lazyweb list of recently infected repos, although there are only ten results returned, with no pagination. That's a bit less than the 2.3 million commits reported in the web UI
1 biner88/chart_sparkline
1 davidray/twitter-bootstrap-calendar
1 laudspeaker/laudspeaker
1 ripienaar/free-for-dev
4 segmentio/action-destinations
2 uptech/flutter_app_analytics
(etc)
Also author:claude is of course but one vector for the hungry ghosts... 
ID Claude Users
I just chuckled inside@mcc Consider the following as well:
https://github.com/cursoragent
https://github.com/gemini-code-assist
Copilot doesn't let you block it unfortunately.
@lanodan @nick @mcc gdb will most likely also adopting the same wording as binutils due to the overlap usage of bfd.
As far as mesa and other gui runtimes stuff, that needs to be redone. Gcc or something more. Right now from what I remember Mesa depends on older versions of llvm due to api instability too.
With respect to clang-format, there is some work going on dealing with gcc a68 which might be reused with c/c++ frontends too
@porglezomp @lanodan @nick a nice thing about the block warning is assuming microsoft did not code it in an absurd way, the block warning surely applies only to commits in the past of the current branch.
this would be improved if github had not exempted the copilot bot from blocks. they did exempt it from blocks, and if you look in the github feedback forum there's a feature request from me for the day they did it asking them to not-exempt it. oh well…
@lanodan @nick @mcc that's not true.. they can and historically have used GCC, just preferred to migrate when they could.
freebsd changed from gcc to clang as default for main architectures in 2012 but didn't stop shopping gcc until 2020.
openbsd moved to clang in 2018-2020
nerbsd still uses gcc as default
@nick @mcc thankfully the swift project's fork of LLVM is clean for now:
(or at least, it hasn't been touched by claude yet)
https://github.com/swiftlang/llvm-project
@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