Org assignment for config identities happens only in the org upgrade, and API-created identities are assigned at creation. A name added to config.toml later has no org. Done when every bootstrapped identity is assigned to an org on boot, idempotently.
Close reason
AssignDefaultOrgIdentities now also runs after the recorded upgrade phases, idempotently, and bootstrap runs before it at boot
Imported from beads archie-core-n5yj5 · GitHub #1640 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-13
Org assignment for config identities happens only in the org upgrade, and API-created identities are assigned at creation. A name added to config.toml later has no org. Done when every bootstrapped identity is assigned to an org on boot, idempotently.
### Close reason
AssignDefaultOrgIdentities now also runs after the recorded upgrade phases, idempotently, and bootstrap runs before it at boot
---
_Imported from beads `archie-core-n5yj5` · GitHub #1640 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-13_
sam
added the mediumbug labels 2026-10-27 13:40:30 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Org assignment for config identities happens only in the org upgrade, and API-created identities are assigned at creation. A name added to config.toml later has no org. Done when every bootstrapped identity is assigned to an org on boot, idempotently.
Close reason
AssignDefaultOrgIdentities now also runs after the recorded upgrade phases, idempotently, and bootstrap runs before it at boot
Imported from beads
archie-core-n5yj5· GitHub #1640 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-13