co-authorship implies ability to hold author rights, which afaik an algorithm can't do.
are folks adding speakeasy/stainless co-authorship lines to their commits? should i add alembic as a co-author after making some changes to the database schema?
Co-authored-by: buf generate <noreply@github.com>assume no deep learning, of any kind is involved: you write a program, you are the author, right? you compile the code, are you still the author? do you have to attribute co-authorship to gcc/llvm/oracle?
i think not, you are still the author, same as when anyone else uses an llm to write code.
ianal
this does not seem to match reality, see:
1. count for claude as co-author: 25M
2. count for speakeasy as co-author: 917
3. count for stainless as co-author: 6.2k
4. count for alembic as co-author: *Your search did not match any commits*
ex. search: https://github.com/search?q=%22Co-Authored-By%3A+Claude%22+%...I agree. It's both an ad and a useful signal of where the code came from or how it was created.
Just like the default iPhone email signature, it's an ad and a hint that the author was typing with their thumbs, so it's probably a brief auto-corrected message for that reason.
Which for my repositories means I want ~95% less of it in my commit history. I'm prepared to round up for simplicity. But to each their own.