That's about as much as I can say offhand. I don't remember any other steps, aside form clicking a "Finished", "OK" or some other such button. That's what gets pasted into the URL textbox for the Existing Remote in VS. Git remote add origin "some HTTPS URL here" Down there, I have a section for Add Your Files, which includes a line like this: That takes you to a fairly busy page that includes a ReadMe.MD down towards the bottom (I seem to remember that GitHub worked this way, as well). In my case, I always go into GitLab and create an repo. Since you have, then Existing Remote is probably right for you, as well. Get to the sign in dialog, enter your GitHub backed Microsoft Account email and press Next (don't click on sign-in options) Click on the ' Email code to. GitHub is an option on that form, so you might be able to just push straight to GitHub, but only if you haven't already gone into GitHub and created an existing repo. Is this best? Since I'm using GitLab, I think it might be my only option. This brings up a form that allows you to choose the new remote or to push to an existing remote. That has the option to Create Git Repository (or clone one). When I create a new project (or have an existing project) that I want to push to GitLab, there is a Git Changes tab by Solution Explorer (it's one of the tabs, for me, though I have never bothered to see if it is it's own entity, so I always thought it was part of Solution Explorer). Still, these are the steps I (think) I follow for GitLab: I think they are virtually the same, so the steps for one are likely much like, or the same to, steps on the other. The rules for GitHub and GitLab seems to change every other year, or so. There are numerous options and approaches, of which I use very few.įirst off, I use GitLab because I prefer the fact that I can create numerous private repos. I thought I could provide a better set of steps, but now that I look at it, I think I'll leave a bunch out.
0 Comments
Leave a Reply. |