<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div dir="ltr">Hi Chris,<div><br></div><div><div>> following the instructions at<br></div></div><div><div>> <a href="https://help.github.com/articles/fork-a-repo">https://help.github.com/articles/fork-a-repo</a> doesn't work .</div>
</div><div><br></div><div>The article you want is:</div><div><a href="https://help.github.com/articles/create-a-repo" target="_blank">https://help.github.com/articles/create-a-repo</a><br></div></div></blockquote><div><br></div><div>I did this article and created the README yesterday, which created a Hello-World folder on my computer with a .git and a README file. I couldn't commit or push the commit due to the errors I sent you yesterday (remote origin already exists). But that article is only about creating a repo and creating and pushing a README file. It says nothing about cloning to my local workstation.</div><br><blockquote type="cite"><div dir="ltr"><div>*not* the one on forking a repo. The forking article is when you want to make a copy of someone *else's* repository and work on your copy of it. In your case, it is your own repo that you control. So you need to:</div>
<div>A) create the repo on GitHub (you did this already)</div><div>B) clone it to your local workstation (that's what "git clone" does; you can also do it via GitHub for Mac or other UI)</div><div>
C) hack on the local copy on your workstation</div><div>D) commit your changes, which is like taking a snapshot so you don't lose work</div><div>E) push your commits back to the remote server, so others can see what you did</div>
<div><br></div><div>Pushing your changes back to GitHub is also nice in case your computer explodes, so you don't lose any work. You won't even lose the *history* of your work since the entire thing is there on the server. (And the entire thing is there on you local workstation -- that's why it's called a "clone").</div></div></blockquote><div><br></div><div>I need instructions on how to do steps B through E.</div><div><br></div><blockquote type="cite"><div dir="ltr"><div>> I'm still lost and do not want to start trying things without knowing</div><div><div><div>> what I'm doing.</div></div><div><br></div><div></div></div><div>I strongly suggest you take the time to read up on Git so that you have a basic understanding before you flail around too much. It will save you a lot of frustration.</div>
<div><br></div>
<div><a href="http://git-scm.com/book" target="_blank">http://git-scm.com/book</a><br></div><div><br></div><div>Regards,</div><div>Curtis</div></div></blockquote><br></div><div>Thanks, Curtis, I will definitely study this.</div></body></html>