You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Skip adding remotes when repo already exists during clone
When cloning, if a repo already exists, the clone operation is skipped
entirely - including not attempting to add any remotes. Previously,
clone would skip the git clone but still try to add remotes, which
would fail with "remote xxx already exists" warnings.
Changed Git::clone() to return Result<bool, GitopolisError> where true
means the repo was cloned and false means it was skipped (already exists).
Prompts:
- "now fix this bug [shouldn't add extra remotes to existing repo when cloning · Issue #247 · timabell/gitopolis](#247)"
- in response to suggestion about checking existing remotes: "simpler than that, if a repo already exists don't clone it and don't add any remotes"
Fixes#247
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments