Phase 2 console side, for inbuxa-server's inbuxa:AccountLock.
Compliance > Locked accounts: every locked account with who locked it, when and why, and its delegates.
Lock, edit delegates and unlock dialogs; each needs a reason.
A person's account page shows the lock, with lock or unlock.
Account pickers everywhere now label accounts by full address. The bare local part made the same name in two domains indistinguishable, and a lock landed on the wrong account in testing.
Typecheck, lint and 408 tests pass; checked in Chrome against a local server.
Phase 2 console side, for inbuxa-server's `inbuxa:AccountLock`.
- Compliance > Locked accounts: every locked account with who locked it, when and why, and its delegates.
- Lock, edit delegates and unlock dialogs; each needs a reason.
- A person's account page shows the lock, with lock or unlock.
- Account pickers everywhere now label accounts by full address. The bare local part made the same name in two domains indistinguishable, and a lock landed on the wrong account in testing.
Typecheck, lint and 408 tests pass; checked in Chrome against a local server.
Management > Compliance > Locked accounts lists locked accounts and their
delegates, with lock, edit delegates and unlock dialogs that require a
reason. A person's account page shows the lock and the way to lock or
unlock it (audit-hold-lock spec AL-1, AL-5).
An account's name is only its local part, so leslie.ritchie in two
domains looked the same in every account picker; locking picked the
wrong one. Account options and labels now use the full address.
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.
Phase 2 console side, for inbuxa-server's
inbuxa:AccountLock.Typecheck, lint and 408 tests pass; checked in Chrome against a local server.