Use GitHub contributor list to detect more AI #1

jacksonchen666 commented 2025年12月22日 13:05:58 +01:00

https://api.github.com/repos/Floorp-Projects/Floorp/contributors?per_page=100 single API call, github apps show up too, https://docs.github.com/en/rest/repos/repos?apiVersion=2022年11月28日#list-repository-contributors

use ID or node nonsense? prefer files first or prefer contributors first? (or user setting?)

---

If you have examples of projects using "AI" in a way that's visible in the contributors list on GitHub, please share a link in the comments for this issue! (I'm collecting all the "AI" bots)

https://api.github.com/repos/Floorp-Projects/Floorp/contributors?per_page=100 single API call, github apps show up too, https://docs.github.com/en/rest/repos/repos?apiVersion=2022年11月28日#list-repository-contributors use ID or node nonsense? prefer files first or prefer contributors first? (or user setting?) --- If you have examples of projects using "AI" in a way that's visible in the contributors list on GitHub, please share a link in the comments for this issue! (I'm collecting all the "AI" bots)

jacksonchen666 commented 2025年12月22日 13:46:06 +01:00

https://github.com/benbjohnson/litestream

https://github.com/benbjohnson/litestream

jacksonchen666 commented 2025年12月22日 13:59:30 +01:00

notable thing from the API:

"html_url": "https://github.com/apps/google-labs-jules",

html_url is otherwise link to user profile

notable thing from the API: > "html_url": "https://github.com/apps/google-labs-jules", html_url is otherwise link to user profile

jacksonchen666 commented 2025年12月22日 17:16:22 +01:00

one case that may be interesting to look at is https://github.com/home-assistant/core which has way too many contributors (ignoring the files)

one case that may be interesting to look at is https://github.com/home-assistant/core which has *way too many* contributors (ignoring the files)

jacksonchen666 commented 2025年12月22日 17:20:02 +01:00

can't forget to mention niri accepted a PR with Claude as coauthor

can't forget to mention [niri accepted a PR with Claude as coauthor](https://github.com/YaLTeR/niri/pull/2109)

0x4261756D commented 2025年12月23日 22:34:25 +01:00

When taking a shot at implementing this I noticed that the contributors API seems to omit some users sometimes. https://github.com/benbjohnson/litestream/graphs/contributors displays 25 contributors, including claude, https://api.github.com/repos/benbjohnson/litestream/contributors?per_page=100 only lists 21, excluding claude. For Floorp, however, Copilot does show up.

When taking a shot at implementing this I noticed that the contributors API seems to omit some users sometimes. https://github.com/benbjohnson/litestream/graphs/contributors displays 25 contributors, including claude, https://api.github.com/repos/benbjohnson/litestream/contributors?per_page=100 only lists 21, excluding claude. For Floorp, however, Copilot does show up.

jacksonchen666 commented 2025年12月27日 10:29:10 +01:00

https://github.com/ArcaneChat/android

https://github.com/ArcaneChat/android/pull/87 resulted in github.com/ArcaneChat/android@76e4c59119 which has no copilot indications

https://github.com/ArcaneChat/android https://github.com/ArcaneChat/android/pull/87 resulted in https://github.com/ArcaneChat/android/commit/76e4c59119ab40c124ba50b1c85659c04fd1bde9 which has no copilot indications

0x4261756D commented 2025年12月27日 14:12:48 +01:00

I guess a heuristic for that would be the commit message "Merge pull request #\d+ from <repo name>/copilot/<branch name>" which is very unlikely to produce false positives. Checking the parent commits themselves would sadly incur more API calls because the API only contains the parents' hashes.

I guess a heuristic for that would be the commit message "Merge pull request #\d+ from \<repo name\>/copilot/\<branch name\>" which is very unlikely to produce false positives. Checking the parent commits themselves would sadly incur more API calls because the API only contains the parents' hashes.

0x4261756D commented 2025年12月27日 14:33:15 +01:00

I have updated my branch. It now also catches those merge commits

I have updated my branch. It now also catches those merge commits

jacksonchen666 commented 2026年01月10日 02:25:52 +01:00

Contributors check implemented as the last check in v0.2.0.

Contributors check implemented as the last check in v0.2.0.

fzzr commented 2026年04月24日 16:11:03 +02:00

Currently (actually latest version) ignores https://github.com/niri-wm/niri/pull/2109/changes/6f695feb869455c5af4dac9e437a019e685286d3 and doesn't reports it :(

Currently (actually latest version) ignores https://github.com/niri-wm/niri/pull/2109/changes/6f695feb869455c5af4dac9e437a019e685286d3 and doesn't reports it :(

jacksonchen666 commented 2026年04月24日 20:28:28 +02:00

@fzzr:

• Commits detection is only limited to the last 100 commits (max that GitHub allows in 1 API request). There has been 474 commits already since the thing you linked. So the userscript won't be able to detect something too far in the past.
• If there are issues, and none of the existing issues precisely match the problem, please create a new issue instead, not comment on existing ones.

@fzzr: - Commits detection is only limited to the last 100 commits (max that GitHub allows in 1 API request). There has been 474 commits already since the thing you linked. So the userscript won't be able to detect something too far in the past. - If there are issues, and none of the existing issues precisely match the problem, please create a new issue instead, not comment on existing ones.