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

Path to reference 'branchName' collides with existing one. Error. #886

Closed
NikKovIos opened this issue Dec 16, 2022 · 5 comments
Closed

Path to reference 'branchName' collides with existing one. Error. #886

NikKovIos opened this issue Dec 16, 2022 · 5 comments

Comments

@NikKovIos
Copy link
Contributor

NikKovIos commented Dec 16, 2022

When trying to fetch all (CMD+SHIFT+F) there is an error.

path to reference 'refs/remotes/origin/branchName' collides with existing one

With terminal command git fetch everything works well. git prune didn't fix it.

Version 1.3.2 (1045)

@lucasderraugh
Copy link
Collaborator

Hmm, this does seem to be a new issue, though not reproducible all the time for me. If you have more details on how to reproduce that would be good to know.

@NikKovIos
Copy link
Contributor Author

Close because hard to reproduce.

@lucasderraugh
Copy link
Collaborator

I'm not sure that's a good reason to close it. There are definitely some issues with fetching with the libgit2 changes, I think I'll keep this open as I need to investigate some of these. Worst case I might be reverting everyone back to a 1.3.2 build as the libgit2 changes evidently broke a number of things that weren't caught in tests or during continuous release time.

@lucasderraugh lucasderraugh reopened this Dec 16, 2022
@NikKovIos
Copy link
Contributor Author

Our repo was copied from another. So some branches was from another repo. There is a branch called bug/IOS-233 a year ago. git checkout bug/IOS-233 not see it with error: error: pathspec 'bug/IOS-1223/timeInPlayerAfterRewind' did not match any file(s) known to git. And there is a fresh branch buh/IOS-233/someTitle. It exist and it's a branch name from error.

Dark story. 😣

@lucasderraugh
Copy link
Collaborator

I believe this should be resolved in 1.3.5. Please reopen if this isn't the case and if you can provide any concrete steps for reproduction, it would be very beneficial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants