made the butt shout

[lauralstephenson]

No description provided.

[StephenMayeux]

Good but don't forget your semicolons!

[lauralstephenson]

Stephen,

I am sorry to bother you as I know you are crazy busy. I am hopelessly
confused about Git Bash. Reading documentation online has only deepened my
confusion. Could you give me a paragraph or two of explanation?

Thanks!

Laura

On Mon, May 23, 2016 at 12:55 AM, Stephen Mayeux notifications@github.com
wrote:

Good but don't forget your semicolons!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#5 (comment)

[StephenMayeux]

Happy to help. What are you trying to do? What we did last week?

Sent from my iPhone

On May 28, 2016, at 6:44 PM, Laura Stephenson notifications@github.com wrote:

Stephen,

I am sorry to bother you as I know you are crazy busy. I am hopelessly
confused about Git Bash. Reading documentation online has only deepened my
confusion. Could you give me a paragraph or two of explanation?

Thanks!

Laura

On Mon, May 23, 2016 at 12:55 AM, Stephen Mayeux notifications@github.com
wrote:

Good but don't forget your semicolons!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#5 (comment)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[lauralstephenson]

Stephen,

Yes. I'm trying to share a file on GitBash with Lee Kelly. As you may
remember, we tried and it didn't work. The documentation I've found is sa
clear as mud.

Laura

On Sat, May 28, 2016 at 11:20 PM, Stephen Mayeux notifications@github.com
wrote:

Happy to help. What are you trying to do? What we did last week?

Sent from my iPhone

On May 28, 2016, at 6:44 PM, Laura Stephenson notifications@github.com
wrote:

Stephen,

I am sorry to bother you as I know you are crazy busy. I am hopelessly
confused about Git Bash. Reading documentation online has only deepened
my
confusion. Could you give me a paragraph or two of explanation?

Thanks!

Laura

On Mon, May 23, 2016 at 12:55 AM, Stephen Mayeux <
notifications@github.com>
wrote:

Good but don't forget your semicolons!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
<
#5 (comment)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#5 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AOehz0MI9OauBVlsjyh1Fv5a2yvr2nNlks5qGE8vgaJpZM4Ij7Zd
.

[StephenMayeux]

Some steps and questions to ask yourself

1. Have you created a local repo on your computer using git init? If so, proceed to step 2.
2. Have you created a remote repo on GitHub? If yes, proceed to step 3.
3. Have you "linked" your local repo to your remote repo by using git remote add origin YOUR_GITHUB_REPO_URL ? If not, do that now.
4. If step 3 doesn't work, are you sure you're in the right directory? 9 times out of 10 you're not in the right directory in Git Bash. Type pwd in the terminal and that will print the current working directory. If you are not in the correct directory, you will have to cd into it. Or I believe you can right-click any folder on Windows and select Open With Git Bash
5. Once you are in the correct directory and have set up your remote pointing to the GitHub repo, you are ready to share commits with Lee.
6. Make changes to the files and save them.
7. git add . Pay attention to the spacing. It's important.
8. git commit -m "message detailing the changes you made. keep in present simple tense"
9. repeat steps 7 and 8 as needed.
10. When you are finally ready to upload these changes to GitHub, type git push origin master
11. Do your happy dance.