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 project

Synopsis

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.
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Oct 30, 2018 01:21 PM
Updated by: