Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes # 1861 on Pharo : location not a git repo when Importing existing clone #1862

Merged
merged 3 commits into from
Dec 4, 2024

Conversation

AlexisCnockaert
Copy link
Collaborator

@AlexisCnockaert AlexisCnockaert commented Nov 25, 2024

Fixes #1861
Actually maybe the accept method is a bit full now, but I think it's the easiest way to have the wanted behavior.
@Ducasse now when selecting a location that is not a git repo we just have this :
Screen Shot 2024-11-25 at 14 25 03

@AlexisCnockaert AlexisCnockaert changed the title Fixes the issue 1861 on Pharo Fixes # 1861 on Pharo Nov 25, 2024
@AlexisCnockaert AlexisCnockaert changed the title Fixes # 1861 on Pharo Fixes # 1861 on Pharo : location not a git repo when Importing existing clone Nov 25, 2024
@jecisc jecisc merged commit 4b795a1 into pharo-vcs:Pharo13 Dec 4, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

import from existing clone should be more robust
2 participants