Configuring it is overly complex, poorly documented, and the defaults make no sense at all. It cost me at least a day to set it up, but even so I wasn't able to get it to do anything that dependabot can't do, i.e. update pyproject.toml or any of the .lock files besides uv.lock. It's probably possible, but based on my experience so far, figuring out how will likely take me more time than it'll save.
It's very spammy, and pretends to be me for some reason. I really don't like that, and might even go against the github policies. It also makes it so that I don't get notified when it's behaving like a vicious spambot that keeps opening issues every 5 minutes while I'm asleep.
I have no words for the stupidity behind this design choice, which judging by the docs appears to be intentional...
So I think it's best we pull the plug.
I've already disabled the gha workflow, since it kept re-opening the same PR after closing it, even though I'm already working on that in #708.
Configuring it is overly complex, poorly documented, and the defaults make no sense at all. It cost me at least a day to set it up, but even so I wasn't able to get it to do anything that dependabot can't do, i.e. update
pyproject.tomlor any of the.lockfiles besidesuv.lock. It's probably possible, but based on my experience so far, figuring out how will likely take me more time than it'll save.It's very spammy, and pretends to be me for some reason. I really don't like that, and might even go against the github policies. It also makes it so that I don't get notified when it's behaving like a vicious spambot that keeps opening issues every 5 minutes while I'm asleep.
I have no words for the stupidity behind this design choice, which judging by the docs appears to be intentional...
So I think it's best we pull the plug.
I've already disabled the gha workflow, since it kept re-opening the same PR after closing it, even though I'm already working on that in #708.