Skip to content

Mismatch of local repo name, after cloning (bundle) without specifying one #1460

Closed
@goran-w

Description

@goran-w

I tested cloning from a local git-bundle file, which works well EXCEPT for the fact that SourceGit then tried to open the new clone using the wrong path. However, this only happens when I leave the optional Local Name field empty - if I specify a Local Name, everything works perfectly fine.

When leaving out Local Name and cloning from the filename repo.bundle, Git creates the new clone (directory) with the name repo, but SourceGit tries to open the new clone assuming the name is repo.bundle.

(NOTE: I'm not sure if this issue is specific to how Git deducts clone-names from bundle-files, or if the same issue could arise in other cases where the clone-source has a "dot + extension" file/dir-name...)

Image

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions