I'm not sure can still a reliable way create a map between project PHID and name. That should be the first thing to investigate.

Issue has disappeared since.

If we want to have it in the multi-services container, run like a charm through runit, without any need for the environment:

PhabricatorBot support has been removed upstream in 2017 - https://secure.phabricator.com/rP5c1e4488dedafda08684b33a8a4786cf687d2811

Phabricator IRC bot support has been removed in 2017.

Refactored and committed to rRESOLVEHASH as D2569 / 34835825f734.

As a workaround, I've compiled Git to 2.35.1 inside DevCentral container.

In T1547#23264, @dereckson wrote:

If we upgrade image to bullseye, we'll also get Git 2.30.2, but I've a 403 currently with current Dockerfile at D2522, so needs to investigate.

If we upgrade image to bullseye, we'll also get Git 2.30.2, but I've a 403 currently with current Dockerfile at D2522, so needs to investigate.

We need this, as container still runs on Jessie, and, as such, doesn't provide a recent enough Git version to be compatible with Phabricator.

Timeout for migration.

DNS configuration

Fixed per previous commit and a change in D2465.

Hound works fine, but can't discover default branch of a repo, even with "detect-ref": True

I'd like to test Hound so I need that one this evening.

Spambots actually target Phabricator, so we're fine with the current process.