Closed nzero closed 11 years ago
hello ze-hobbit.
Section 5 is the steps to setup your fork for development so you can push changes back up to your fork.
On your fork page you see three buttons: HTTP, SSH and Read-only. The SSH method requires you to setup a ssh key with gitHub first as shown here.
The HTTP url also works as you saw, the difference is HTTPS might prompt for your github password when you push changes up, where the SSH logs in automatically with the keys.
Since you got it working, you can keep it as is. If you find the password prompt annoying you can easily follow the steps in the link above to add a key, and then add the SSH url to your local repo with:
git remote add --track master origin git@github.com:<username>/dungeons.git
edit: fixed the command above
For info on these urls see: https://help.github.com/articles/which-remote-url-should-i-use
I will add this information to the file to make it clearer. Thanks :)
On check-in with you guys: I merged Wesley's updated install page with the master, which should help anyone else that runs into this issue with getting used to git. Please take the time to review it and ensure that it makes sense to YOU. Git is difficult to become accustomed to, but once you start using it, it all starts to make a great deal of sense. If you think that the modified files are descriptive enough, feel free to close out this issue. If not, then let us know what needs to be said.
Edit: Also, it is possible to use an Android phone to ssh connect and do commit message editing. I wouldn't want to have to do much this way, but it IS possible.
following the install tips, in section 5.2 after forking the project I couldn't clone my fork with
This was what happened:
So I cloned it the same way it was done for DebianJoe's dungeon in section 1
but changed "DebianJoe" for my username and everything worked after that