![]() I'll update some files and commit changes. Now that we have a place to work, let's start making changes. In my repo, I see the same view as I have on the left side of VS Code. I like keeping things separate, so I'll open a new one. Once I do this, I get a note asking if I add this folder to my workspace or a new one. I'll hit "Select Repository Location" here. On my latest machine, I've just created a git folder under Documents. Specifically, so much stuff starts in Documents, especially editors, that I decided to stop doing this. In terms of organization, I used to use c:\Users\serNameSource\Repos for organization, but I found this to a pain. This is where I can pick the folder in which the repo will clone. Once I hit Enter, I get a folder browser. If I select this, I can then enter a GH repo URL. In a new VS Code instance, I can invoke the command palette with CTRL+Shift+P. I see this:įrom here, I want to get a copy of this on my local system. This gives me a repo with one commit, for my README. I'll add a description and initialize with a README. I'll use the /new link to build the new repo. ![]() For the demonstration, I'm going to create a "RedgatePoSh" repo, since I need to manage some demo scripts that use PoSh for various. Someone on the team will create a repo on on GitHub and add all your team members as contributors. The first thing we need to do is create a place to store our code. ![]() We covered some of this in the first article, so check there if you need help getting started. There is documentation available for a VCS and VS Code, but we'll keep things simple in this article. VS Code is a nice editor for PowerShell, and includes VCS features. We will still use GitHub for storing code, but we'll edit and manage our repo in the command line and with VS Code. In this series, we've used GitHub and SourceTree to do some of the work, but we'll diverge a bit here. Note that there are other ways to do this, but I am aiming to keep things simple and easy to implement. Those are fairly simple goals for our team, and this article will walk through how this can work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |