feat(ssh): clone over SSH natively in ssh mode - no HTTPS URL construction, no credential resolution #293
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#293
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #187 (SSH-only mode epic). Depends on the protocol-mode slice.
Under
protocol=ssh(either ssh mode),madtea clone owner/repobuilds the SSH form (git@host:owner/repo.git) instead of HTTPS, andmadtea clone git@host:owner/repo.gitworks as first contact - no credential resolution, no GIT_ASKPASS wiring, no HTTPS fallback on failure. SSH failures surface ssh's own stderr plus a pointer to the preflight.Acceptance:
owner/reporesolves the forge host as today but emits the SSH URL formauth use-sshremains the migration tool for existing HTTPS clones and is cross-referenced