Post

Jake Bailey
@jakebailey.dev

oh no, all this force pushing put me on the AgentScan list

Jake Bailey@jakebailey.dev

please you must understand this is not a mental breakdown this is my life now

0 reposts13 likes

Matteo Gabriele
@matteogabriele.npmx.social

Unfortunately, you have to deal with a lot of limitations and rate-limiting dances to get enough data from GitHub's API. The tool is there to help. Also, I already told Jake he was flagged as "mixed", which, at the end of the day, is true since he was using automations, whether in his repos or not.

Jake Bailey
@jakebailey.dev

Hm, we had a function app using those fields even up to this past month, and org association is public already, I'm a bit confused but maybe this is on different events

Jake Bailey
@jakebailey.dev

Unfortunately yes, though it's more of a display issue in the userscript someone else made that I was trying Just funny to see myself marked as "AI" Each automatic megamerge rebase pushes something like 50 commits, so, not good!

Bjorn Lu
@bluwy.me

Userscript author here 😅 I thought about hiding the label in your own repos, but ultimately it could still appear if you open PRs in other repos, so I figured it's better to be general and consistent to show it as is.

Bjorn Lu
@bluwy.me

I think the agentscan "engine" needs to account for own repos and stacked PRs better, but IIUC the GitHub events to analyze have limitations around that. But also, maybe the userscript can use a lesser strong word to describe mixed signals as @matteogabriele.npmx.social brought up recently.