Migration 0028 claims the bot account unconditionally:
INSERT INTO users (username, is_admin) VALUES ('gitbay-bot', 0);
The name was not reserved before that migration, so an instance upgrading from v1.0.x may already have a user holding it. Then the insert hits the UNIQUE constraint on =users.username=, the migration aborts, and the daemon does not start — a total outage caused by an optional feature.
An org of that name is a quieter version of the same problem: the insert succeeds and the instance ends up with a user and an org sharing one owner name, which the URL space cannot represent.
Neither is reachable on this instance, where the name happened to be free and is now reserved. It is reachable on any other instance upgrading to the release that first carries 0028, and the mirror makes the code public.
Claim the name only when it is free. A dependency check that reports why it cannot open an issue is a far better failure than a forge that will not boot.
closed by commit 0413b92f9a by cmc: Claim the bot's name only when it is free
2026-08-31 16:33 UTC