Phase-3 review (LOW/correctness, flagged by BOTH domain + UI reviews). Account id is the primary key but is built from a trim-only, non-lowercased email: MailProvider.createAccountid="imap:${email.trim()}" (MailProvider.kt:117), ManualSetupViewModel(:67), AppPasswordViewModel.testAndSave, and Account.outlookid="outlook:$email". So User@Gmail.com then user@gmail.com → two account rows syncing the same mailbox (major providers are case-insensitive). Fix: lowercase the address (at least the domain; whole address for consumer providers) when composing the id, so identity is stable across casing. Outlook path is safer (email comes from the id token) but normalize there too for consistency.
Phase-3 review (LOW/correctness, flagged by BOTH domain + UI reviews). Account id is the primary key but is built from a trim-only, non-lowercased email: `MailProvider.createAccount` `id="imap:${email.trim()}"` (MailProvider.kt:117), `ManualSetupViewModel`(:67), `AppPasswordViewModel.testAndSave`, and `Account.outlook` `id="outlook:$email"`. So `User@Gmail.com` then `user@gmail.com` → two account rows syncing the same mailbox (major providers are case-insensitive). **Fix:** lowercase the address (at least the domain; whole address for consumer providers) when composing the id, so identity is stable across casing. Outlook path is safer (email comes from the id token) but normalize there too for consistency.
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-3 review (LOW/correctness, flagged by BOTH domain + UI reviews). Account id is the primary key but is built from a trim-only, non-lowercased email:
MailProvider.createAccountid="imap:${email.trim()}"(MailProvider.kt:117),ManualSetupViewModel(:67),AppPasswordViewModel.testAndSave, andAccount.outlookid="outlook:$email". SoUser@Gmail.comthenuser@gmail.com→ two account rows syncing the same mailbox (major providers are case-insensitive). Fix: lowercase the address (at least the domain; whole address for consumer providers) when composing the id, so identity is stable across casing. Outlook path is safer (email comes from the id token) but normalize there too for consistency.