It looks like the status/need-triage label was removed

Heh. This reminds me of the time when our newly hired "Salesforce Expert" improved our support queue:

  Every time Support received a new email, a ticket in Salesforce would be created and assigned to Support
  
  Every time Support was assigned a new ticket, Salesforce would send a notification email

It's easy to miss, but in the middle of the page:

> 4609 remaining items

Seems gemini-cli and gemini-cli didn't understand who themselves were, so they though someone else added/removed the label, which it tried to correct, which the other then tried to correct, which the other...

Considering that that repository has what seems like ~10 longer term contributors, who probably get email notifications, together with a bunch of other people who get notifications about it, wonder how many emails were sent out because of this? If we just assume ten people get the emails, it's already 46K emails going out in under 24 hours...

Also, who pays for the inference of this gemini-cli? Clicking the "user" links to https://github.com/apps/gemini-cli, and it has a random GitHub user under "Developer", doesn't seem like it's a official Google project, so did someone pay for all of these inference calls here? That'd be a pretty sucky bill to pay...

A similar issue made HN last week, same repo, where an AI bot was having the same kind of argument with itself over and over on an issue. Someone mentioned: This sort of thing is why RAM is 800 bucks now.

This issue seems to involve Gemini-cli[bot] squabbling with itself, adding and removing the label from the issue (leaving contradictory explanation comments to itself each time) for a good 4,600 rounds

> 4610 remaining items

Normally I would complain about people spamming in GitHub issues but I don't think it will matter this time

Finally an example of AI doing something useful. Imagine having to add and remove all those tags 4500+ times by hand!

Classic CI bug with a flair of LLM fun! We had something similar creep into our custom merge queue a few weeks back.

So much productivity accomplished here! Those are numbers management loves to see.

gemini-cli did much more work in this PR then the author himself.

Today github labels, tomorrow paperclips?

in the old days one would add and check for a loop detection token when loops like this could be driven by external systems... i wonder if today it would be as simple as adding "ensure you don't get stuck in any loops" to a prompt.

fwiw. doesn't look like gemini at all, the responses are perfectly canned... maybe just good old fashioned ci rules.

Project admins setting up automation: https://youtu.be/B4M-54cEduo?t=102

The automation: https://youtu.be/GFiWEjCedzY?t=51

It's not wrong.