Help adding new angular project to azure repo (Git/VsCode)
I get really frustrated when i have to add a new project to azure repo using Git. Because I have to create the angular project first in vs code. Then when i add it to azure repo I dont have authority so someone has to create the repo for me. But when i connect to he remote repo all my local files from doing ng new disappear. Because im connected via GIT to the new azure repo.
Ideally i would clone the new azure repo the admin created. But then I cant do an NG NEW because i already have a project folder!?
Hope someone can help.
Ideally i would clone the new azure repo the admin created. But then I cant do an NG NEW because i already have a project folder!?
Hope someone can help.
Yujin Boby
You can clone the repo, then copy over the project files you created and commit the new files to the repo and push it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow very good suggestions I will remember this everytime i get started on a proj in vs code and want to use git to push to a naked azure repo.
Thanks!
Thanks!
You are welcome :) (I do remember my first times with Git.)
My experience is that it is better to learn Git as it was designed (see https://git-scm.com/book/en/v2), and to get the official distribution of Git (probably using the package tools in your Linux, or by downloading from https://git-scm.com/) for Windows.
The truth is that Visual Studio (the VS Code is derived from it) used other version-control systems. The same holds for various tools and commanders that suppor more than one version-control system. The problem is that the other VCS's may be very different in working with repository, they think differently about branches... So, it is rather problematic to use "common subset" for all known VCS's.
Even though I regularly use Visual Studio, I prefer to use the separate (the official) Git tools. Actually, you can mix both using the tools from the VS Code and the official Git tools. However, I think that the built-in tools in IDE will not help you to understand the core of Git. Git is actually very simple in principle; the built-in IDE tools almost always obscure that native Git simplicity (in my opinion).
My experience is that it is better to learn Git as it was designed (see https://git-scm.com/book/en/v2), and to get the official distribution of Git (probably using the package tools in your Linux, or by downloading from https://git-scm.com/) for Windows.
The truth is that Visual Studio (the VS Code is derived from it) used other version-control systems. The same holds for various tools and commanders that suppor more than one version-control system. The problem is that the other VCS's may be very different in working with repository, they think differently about branches... So, it is rather problematic to use "common subset" for all known VCS's.
Even though I regularly use Visual Studio, I prefer to use the separate (the official) Git tools. Actually, you can mix both using the tools from the VS Code and the official Git tools. However, I think that the built-in tools in IDE will not help you to understand the core of Git. Git is actually very simple in principle; the built-in IDE tools almost always obscure that native Git simplicity (in my opinion).