<div dir="ltr">Hi Chris,<div><br></div><div>> <span style="font-family:arial,sans-serif;font-size:13px">I need instructions on how to do steps B through E.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><font face="arial, sans-serif">You already have the clone on your workstation. You wouldn't have been able to push the README otherwise. You probably ran "git init" which actually *creates* the repository on your workstation, and then you ran "git push" which mirrors it back to GitHub. So you don't need to clone in that case; you already have a copy of the repo, since the workstation is where you created it.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Step (D) is "git commit"</font></div><div><font face="arial, sans-serif">Step (E) is "git push"</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">The book and other Git tutorials have more information.</font></div><div><font face="arial, sans-serif"><br></font></div>
<div><font face="arial, sans-serif">You are already really close -- you have the code on your local workstation, you have a GitHub repository already in existence, you have a local Git repository linked to that remote repository, so all you have to do is commit and push.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">The errors you mentioned yesterday were because your local Git repository had the wrong URL for the GitHub remote. That's why I asked you to check the output of "git remote -v". It should say your origin is "<a href="https://github.com/ad1054/Postcards">https://github.com/ad1054/Postcards</a>". If it says "Hello-World" that is wrong. To fix, try this:</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">git remote rm origin</font></div><div><font face="arial, sans-serif">git remote add origin <a href="https://github.com/ad1054/Postcards">https://github.com/ad1054/Postcards</a></font></div>
<div><br></div><div style><font face="arial, sans-serif">Or, as Johannes says: just reclone from your GitHub remote into a new directory, and then copy your files into there, and then commit and push using the GitHub for Mac GUI.</font></div>
<div style><font face="arial, sans-serif"><br></font></div><div style><font face="arial, sans-serif">Don't worry about "screwing anything up" because you can always just delete and recreate the repository. It's not like you're going to lose hundreds of hours of work, here.</font></div>
<div style><font face="arial, sans-serif"><br></font></div><div style><font face="arial, sans-serif">Regards,</font></div><div style><font face="arial, sans-serif">Curtis</font></div>
<div style="font-family:arial,sans-serif;font-size:13px"></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 27, 2013 at 2:07 PM, Chris <span dir="ltr"><<a href="mailto:chris@gaiag.net" target="_blank">chris@gaiag.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="im"><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" target="_blank">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><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>
<div class="im"><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><div>I need instructions on how to do steps B through E.</div><div class="im"><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><div>Thanks, Curtis, I will definitely study this.</div>
</div>
</blockquote></div><br></div>