This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- Code Insight
- :
- Code Insight Knowledge Base
- :
- Unable to use Git connector to create a new project on a GitLab instance
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Unable to use Git connector to create a new project on a GitLab instance
Unable to use Git connector to create a new project on a GitLab instance
Summary
This article discusses the cause of the 'pathspec 'origin/master' did not match any file(s) known to git' error message received when attempting to scan a Git projectSynopsis
When attempting to scan a Git project we encounter the following error:com.palamida.workspace.WorkspaceException: Unable to sync 'testgiturl' before scanning due to error: pathspec 'origin/master' did not match any file(s) known to git.
Discussion
It appears that when the clone is called FlexNet Code Insight is attempting to gather a branch called 'origin-master' which cannot be found resulting in the error message in the attached core.log. This can occur when a branch is only a remote tracking branch and not a local branch (See https://stackoverflow.com/questions/30800454/error-pathspec-test-branch-did-not-match-any-files-known-to-git/33101231). I have also located information on a resolution for this issue from https://medium.com/sudogem/git-error-pathspec-develop-did-not-match-any-file-s-known-to-git-abc71ef39563. As shown in the above link the repo will need to be fetched before attempting clone the repo.
No ratings