


Surely this shouldn't be required, but for some reason it is in this case.A Mac user can face many unwanted events that can result in the loss of precious data. I haven't had to use Git CMD to clone a repository for the last couple of years. The second command populates the folder in question with the proper files, and I'm then forced to do a Force Push from Visual Studio because I've got divergent branches. The only thing that seems to work is to use Git CMD and issuing the following commands: $ git fetch origin masterįrom.

Start Visual Studio (2019 Community in this case).Now, when I try to clone these projects, I cannot for the life of me get the actual files to download using the "standard" workflow, namely: I've since then had to delete the local files due to some rearranging on my local drive. However, a couple of weeks back I added two new projects to DevOps. Whenever we create a new project, we add it to DevOps instead of GitHub, and for existing GitHub repos, we make an import using the DevOps tooling. Goal is to get everything into DevOps before the end of the year. My client has started migrating their various repos from GitHub to Azure DevOps.
