Open pradyunsg opened 3 years ago
I've put one of the deployments into "maintenance mode". I believe the other one handles our newsfile/pr checks, so I'll avoid pulling it down until the replacement is up.
Turns out @pypa/pip-bots had write access. This has been revoked.
@pypa/pip-committers I've removed news-file/pr from the required checks. I have a working rewrite deployed at http://pradyunsg-browntruck.herokuapp.com; that I'll move to our current endpoints to over the weekend.
With https://github.com/pypa/pip/pull/9785 and #10363, I think it's clear that we're going a different direction. :)
Exerpts from a conversation from the PSF Slack's #general
channel:
Heroku's credit program is in a weird flux [snip] If it changes yeah, we'll probably migrate, but it isn't pressing at this time. The bots are a very small portion of our Heroku "spend" and a much lower priority than python.org backend which is pretty substantial.
@pypa-bot and @BrownTruck are hosted on PSF's Heroku credits, so I think moving away from that now would be reasonable.
This is done now.
No, it's not. I missed one important thing: removing the merge conflicts label, on PR update.
Update: We're gonna instead replace them with GitHub Actions.
pypa/browntruck currently has 2 deployed forks.
I'm creating a 3rd version, and will be replacing both of these forks with it; hopefully very soon. Until then, if you see any weirdness, just call it out here.