Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe SSH backend prompt and desktop dialog now describe password or verification-code authentication. Expired prompts use verification-focused wording. Tests cover backend prompt text, dialog copy, key and 2FA wording, and expiration handling. ChangesSSH verification prompt
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Low Suggested reviewers: Merge Risk: ⚪ Minimal · up to The SSH dialog now accurately explains that a server may request either a password or a verification code after key authentication. No actionable merge risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
This should be merged as soon as a core maintainer has time. Clear improvement with solid tests around the expiry wording, thanks for the contribution. |
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — This is a focused clarification of SSH password and verification-code prompt copy, with no change to authentication mechanics or data contracts. Because it modifies production code in the SSH authentication path and its credential prompt UI, it warrants human review. You can add or adjust custom eligibility rules. Learn more. |
|
Note Written by Hi! We are cleaning up open PRs, and this one appears to have been created with an older model ( |
What Changed
The SSH dialog and generated prompt now ask for a password or verification code. The hint explains that SSH keys do not remove a server's second-factor requirement.
Why
Fixes #10784. The previous password-only wording misled users whose SSH key was already accepted and whose server was waiting for a TOTP code. Authentication behavior is unchanged.
Validation: TDD red → green; 59 affected tests pass; web/SSH typechecks and focused lint pass.
UI Changes
Real dialog rendered in the web client with a simulated desktop IPC prompt; no live SSH connection was used.
Checklist
Model: GPT-6. Harness: Codex.
Summary by CodeRabbit
User Experience
Bug Fixes