your github repo url), then you do something like git fetch, and then git asks your for username/password or uses your ssh keys. The advantage is that (a) it's more secure than passwords and (b) you don't have to type in your password manually every time (as long as you also use an ssh-agent).Īs for gh: this is handy for doing the non-git related tasks like creating/deleting repos, issues and PRs etc.Įdit: "how to login", in case it wasn't clear enough above: first you need to configure your remote git remote add … (i.e. Github has nice docs explaining every step. If the protocol is git:// or ssh://, git is using SSH keys. Read the github docs to find out how to use them. (I'm sure it's possible to store the password – encrypted or unencrypted – but I don't remember how).Īnyway, this doesn't help you for Github, because two years ago GH retired passwords in favor of "personal access tokens" for security reasons. I don't know how you didn't discover this. This shows up every time you try to connect to the remote, i.e. ![]() The username defaults to your current system user if nothing else is supplied, the password can be entered via interactive prompt. If the protocol is http(s), git uses user/password auth. Which one is used depends on the protocol you configured to connect with your remote ( git remote -v) You have two main methods of authentication to chose from: user/password and ssh. I thought the whole point of git was to be used across many different systems? Does gitlab have its own version too? How many am I going to need by the end of this? If there's nowhere for passwords to go, what prevents someone from stealing your GitHub account?Īlso, I've found talk of a gh command, but why is that even needed? Why should github have its own special git command. I guess you can just set your username as a variable, but what use is it without the password? Specifically, I can't find a single shred of information on where to enter my password. How are millions of people using this tool when you can't even login with it? How have millions of people found out how to login to this tool when it's nowhere to be found in the documentation? WHERE IS THE SOURCE OF THIS INFORMATION AND WHY ARE BEGINNERS NOT INFORMED OF IT? They just talk about logging in and never get to the point. There are 3 or 4 different guides, all of which have some kind of "logging in" section, yet none of them actually say how to login. I can't comprehend this lack of information. I'm trying to stop relying on the graphical clients, and it's not going well. GitKraken has this neat interface where you can enter your GitHub username and password, and it logs you in as you'd expect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |