Remember last used GitHub, see tips, most recently, three years ago, and are a long pass file, the file is deleted, only to find deleted library, but deleting a directory of library, to die , unless it is downloaded, in the GitHub repository deleted re-add. Using the code deletion, has problems and recorded.
The company previously used Zen, later using GItlab. Gitlab Although relatively similar to GitHub, but unfortunately, I have used a few times, so the use GitHub is a novice, so errors continued.
Question 1: Error while configuring git
I can say the same question Baidu, Baidu found the front configuration, and even now find a little different, the result is that previously failed, and now succeeded.
Now way: configure email accounts and local repository on the command line:
[Root @ localh ~] # git config --global user.name 'github username' # username
[Root @ localh ~] # git config --global user.eamil 'mailbox GitHub bound' Mailbox #
Question 2: Connect GitHub on Linux, a connection error error key value
Solution: At first I thought it was the thought ip problems caused. Because I'm using a virtual machine, IP does not change, so I think yesterday ip generated id_rsa.pub not in use today, was caused by the failure. I once again generated a bind again found or does not help, only to find that my brain axis, this id_rsa.pub and ip does not matter ah, the starting point of error.
Find again, only to find that my warehouse Deploy keys to change the connection. Simply put, you use what the warehouse, it is necessary to set Deploy keys connected to it alone, a Deploy keys can not all be able to use the warehouse, I started to think so.
Question 3: ERROR: Repository not found fatal:. Unable to read remote repository. Make sure you have the correct access permissions and warehouses exist.
Solution: Remote git the SET-url Origin HTTPS: // github.com/. . . . .git
Question 4: error: src refspec Moon does not match any error:. You can not push a number of references to '[email protected]: Username /Moon.git'
Online solutions to find:
Modify .git / config file
thereafter added:
[the receive]
denyCurrentBranch = the ignore
Question 5: The above problem is solved, new problems arise:
Warning: Permanently added 'github.com, 13.229.188.59' (RSA) to at The List of Known hosts.
ERROR: you are at The Key Authenticating with Marked AS has been the Read only.
Fatal: unable to read the remote repository.
Make sure you have the correct access permissions and warehouses exist.
My solution: Setting -> Options -> Danger Zone -> the this Archive Repository, RESULTS: Death
Workaround: Setting -> Deploy Keys
We add ssh when not checked, all need to be removed to re-add ssh, check on the line.
