


Let's say we would like to clone under C:/Git/ and suppose the remote repository name is sg_angular. Step 2c: Navigate to the directory (Use DOS CD command) where the remote Git repository needs to be cloned. Step 2b: Go to View > Integrated Terminal NET Framework 4.5 from Web Installer or Offline Installer. If not, please download & install Git for Windows from. Luckily – it’s simple.After playing with VSC for some time, I found the way to configure VSC with Git in just 5 steps which were easy and straight forward.īefore starting to follow the below 5 steps, please make sure that Git is installed on your system. But still – an unseasoned git user will be baffled.īut… How do you work your way around the issue? 🤔 Solution I mean, to be fair, it’s probably just the way git maintains information about your repository not being very intuitive about odd issues like default branch names not matching. I have no idea where this project got the default branch from, but it failed. If your default/primary/whatever-you-call-it branch is called main, this one won’t do. My new-ish AzDO repository came with the main branch, and didn’t want to have anything to do with primary branches named any other way! Some time ago, Microsoft started provisioning main branches instead of the more traditional master – which admittedly comes with plenty of baggage nowadays – but didn’t automatically update old repositories. Somehow, importing a repo from GitHub to AzDO ended up with the primary branch being called differently, and that threw a wrench to git’s pulling gears big time. Your configuration specifies to merge with the ref 'refs/heads/master'įrom the remote, but no such ref was fetched. The error would be somewhat like this: fatal: no such branch: 'master…master' git pull -tags That didn’t work – instead, Visual Studio Code would throw an error and fail. I had just imported a repository from GitHub (this one, if you’re interested ) to Azure DevOps and tried to pull it locally. So there I was, just following a guide on.
