paolaperaza / vfastronauts Goto Github PK

What

Well, your changes are considered live! The doc is up, and you can cross out that to-do.

How

Add a final comment to that GitHub issue and close it out. You're all set. Bonus points if you were able to point your commit to the GitHub issue the way I did in #13.

What

Ok, so your branch now has your latest work. Let's now push it up "for review" by creating a pull request.

Here, you're essentially saying "ok this is done, someone look it over. If it's good, merge to master!"

How

Instructions here 👉 https://guides.github.com/activities/hello-world/

What

Ok, so you've finished writing, your version is saved on your computer and you're ready to push up those changes to your branch.

Let's do it.

How

First, make sure all of your changes are saved. Then, run the following in your terminal:

1. $ git status
2. $ git add <name of file you changed>
3. $ git commit "commit message #<githubissuenumber>"
4. $ git push

Pro-Tips

• Whenever you're working on anything remote, make sure you're up to date on your current branch (if you're working on a team, someone else might be making changes) by running git pull
• Commit messages are an art. Be specific. Be brief.
• Adding #10 to your commit message associates your commit to the GitHub issue the commit is supposed to address (GitHub issue #10 in this repo aka this issue)
• Example: #13

What

Now that you have access to the latest code, let's create a branch. That'll allow you to:

• Create a copied version of these files
• Make any changes you want on your machine
• Push those changes up to that branch, without affecting "master" (so as to not fuck anything up)
• Whenever you're ready, you can merge your branch with the master branch!

When you "merge" your branch into the "master" branch, the "master" branch is updated (yes there could be issues, aka merge conflicts, here...

How

1. Assign yourself this issue ➡️
2. Create a branch (name it whatever you want)
3. Checkout into that branch
4. Confirm you are now working on that branch (hint: run $ git branch)
5. Close issue!

Pro-Tips

• You should also see your new branch listed if you click into branches on the main page of this repo

• Dug Song, the founder of Duo, gave an inspirational talk about how he went about building the company--he was so intentional about creating a 9-5 work culture that he'd schedule emails to send during those hours so that employees wouldn't know he was working at 2am.

• The IDEO workshop (prototyping is so useful when you want user feedback fast)

• Meeting the Cincinnati fellows for the first time

• Finding out that Amy Nelson is interested in philosophy!

• Building a functioning website for a small business owner that's still online and operational: actually impacting the owner's livelihood

• After training camp, I made my family try Banza, and they liked it--it was fun to be able to feel like I was sharing a (small) part of what VFA could be with them.

• Somebody gave a Pecha Kucha on Hot Cheetos, and it was comedy gold.

• Late night bonding and board games with other fellows

• Trying (with variable success) to explain what Astronomer does to all the fellows who asked. Getting slightly better at explaining what Astronomer does.

• Meeting Natalie Akers

What

GitHub issue is closed, so let's close out that branch you created since it was specific to this project and to-do.

How

Instructions here: https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository.

Pro-Tip

To confirm, run $ git branch from your terminal (remember that branches are specific to github repos, so you have to be in vfastronauts repo from your terminal for it to show up or not).

Once you've closed all of these issues, you can CELLY!!

What

Ok - now that you have this repo on your machine, let's create a fresh new doc in it.

As all things go, the first step is to put it on the to-do list. In our world, that means creating an issue for it (one of these).

Let's create a GitHub issue for creating another file in this repo similar to sample-doc. Within that doc, we're going to make 1 list in Markdown:

• Top 10 Training Camp moments (and why)

How

1. Create a GitHub issue directly from GitHub
2. Assign it to yourself
3. Name it accordingly
4. Give it a description (your instructions to yourself based on the above)

Pro Tips

Making good, concise, actionable GitHub issues is an art. A few resources on how to write awesome GitHub issues:

• https://medium.com/nyc-planning-digital/writing-a-proper-github-issue-97427d62a20f
• https://hackernoon.com/45-github-issues-dos-and-donts-dfec9ab4b612

What

Now that you have access to the latest code, let's create a branch. That'll allow you to:

• Create a copied version of these files
• Make any changes you want on your machine
• Push those changes up to that branch, without affecting "master" (so as to not fuck anything up)
• Whenever you're ready, you can merge your branch with the master branch!

When you "merge" your branch into the "master" branch, the "master" branch is updated (yes there could be issues, aka merge conflicts, here...

How

1. Assign yourself this issue ➡️
2. Create a branch (name it whatever you want)
3. Checkout into that branch
4. Confirm you are now working on that branch (hint: run $ git branch)
5. Close issue!

Pro-Tips

• You should also see your new branch listed if you click into branches on the main page of this repo

What

If you've made sure you're in your newly created branch, let's get to it and create that doc.

How

In your code editor:

1. Create a new doc file (remember to name it <title>.md - the .md will tell it to be in Markdown)
2. Write away (Top 10 Training Camp moments)
3. Save your changes (Just Cmd + S)

What

Ok - now that you have this repo on your machine, let's create a fresh new doc in it.

As all things go, the first step is to put it on the to-do list. In our world, that means creating an issue for it (one of these).

Let's create a GitHub issue for creating another file in this repo similar to sample-doc. Within that doc, we're going to make 1 list in Markdown:

• Top 10 Training Camp moments (and why)

How

1. Create a GitHub issue directly from GitHub
2. Assign it to yourself
3. Name it accordingly
4. Give it a description (your instructions to yourself based on the above)

Pro Tips

Making good, concise, actionable GitHub issues is an art. A few resources on how to write awesome GitHub issues:

• https://medium.com/nyc-planning-digital/writing-a-proper-github-issue-97427d62a20f
• https://hackernoon.com/45-github-issues-dos-and-donts-dfec9ab4b612

What

At this point, you should have a folder somewhere on your machine that's called vfastronauts and contains the content of this repo.

Let's open that folder in your code editor.

How

1. Assign yourself this issue ➡️
2. Open up your code editor on your computer
3. Open up your directory in your Code Editor (File > Open)
4. See the "source code" for this repo's README and sample-doc
5. Close this issue once you're set!

Bonus Points

There's a cool little thing you can install that allows you to just run code . from your terminal within your directory, and it'll open up your code editor automatically.

Instructions here.

What

At this point, you should have a folder somewhere on your machine that's called vfastronauts and contains the content of this repo.

Let's open that folder in your code editor.

How

1. Assign yourself this issue ➡️
2. Open up your code editor on your computer
3. Open up your directory in your Code Editor (File > Open)
4. See the "source code" for this repo's README and sample-doc
5. Close this issue once you're set!

Bonus Points

There's a cool little thing you can install that allows you to just run code . from your terminal within your directory, and it'll open up your code editor automatically.

Instructions here.

What

Ok, so you've finished writing, your version is saved on your computer and you're ready to push up those changes to your branch.

Let's do it.

How

First, make sure all of your changes are saved. Then, run the following in your terminal:

1. $ git status
2. $ git add <name of file you changed>
3. $ git commit "commit message #<githubissuenumber>"
4. $ git push

Pro-Tips

• Whenever you're working on anything remote, make sure you're up to date on your current branch (if you're working on a team, someone else might be making changes) by running git pull. Typically, run this BEFORE you start working on something.
• Commit messages are an art. Be specific. Be brief.
• Adding #10 to your commit message associates your commit to the GitHub issue the commit is supposed to address (GitHub issue #10 in this repo aka this issue)
• Example: #13

What

Let's clone this GitHub repo (paolaperaza/vfastronauts). This will download any files within this repo onto your own computer.

How

1. Assign yourself to this issue ➡️
2. Follow instructions here: https://help.github.com/en/articles/cloning-a-repository
3. Close this issue once you're done!

Pro-Tips

• Make sure you're in the right "directory" (aka folder) when you clone it
• Try creating an "AstronomerCode" folder on your Desktop (name it whatever you want - bonus points if you find out how to create a folder from your terminal), and then throw this GitHub repo in there
• To check where you are at any time, run ls in your terminal
• To jump into any folder you have access to from there (hierarchically lower), run cd <folder name>. E.g. cd Desktop
• If you're in a layer too deep, go one folder back up by running: cd ..
• When you run ls inside of vfastronauts, you should see:
  • README.md
  • sample-doc.md

Paolas-MacBook-Pro:~ paola$ cd Desktop
Paolas-MacBook-Pro:Desktop paola$ ls
vfastronauts
Paolas-MacBook-Pro:Desktop paola$ cd vfastronauts
Paolas-MacBook-Pro:vfastronauts paola$ ls
README.md
sample-doc
Paolas-MacBook-Pro:vfastronauts paola$ cd ..
Paolas-MacBook-Pro:Desktop paola$ 

Need Help? Tag me (@paolaperaza ) and ask away - I'll get a notification for it.

Problem

As a part of this tutorial GitHub repo, we should have a sample standing doc for others to reference.

Solution

Create a sample markdown file in the vfastronauts directory for reference. That doc can just include some sample text.

What

If you've made sure you're in your newly created branch, let's get to it and create that doc.

How

In your code editor:

1. Create a new doc file (remember to name it <title>.md - the .md will tell it to be in Markdown)
2. Write away (Top 10 Training Camp moments)
3. Save your changes (Just Cmd + S)

What

Let's clone this GitHub repo (paolaperaza/vfastronauts). This will download any files within this repo onto your own computer.

How

• Assign yourself to this issue ➡️
• Follow instructions here: https://help.github.com/en/articles/cloning-a-repository
• Close this issue once you're done!

Pro-Tips

• Make sure you're in the right "directory" (aka folder) when you clone it
• Try creating an "AstronomerCode" folder on your Desktop (name it whatever you want - bonus points if you find out how to create a folder from your terminal), and then throw this GitHub repo in there
• To check where you are at any time, run ls in your terminal
• To jump into any folder you have access to from there (hierarchically lower), run cd <folder name>. E.g. cd Desktop
• If you're in a layer too deep, go one folder back up by running: cd ..
• When you run ls inside of vfastronauts, you should see:
  • README.md
  • sample-doc.md

Paolas-MacBook-Pro:~ paola$ cd Desktop
Paolas-MacBook-Pro:Desktop paola$ ls
vfastronauts
Paolas-MacBook-Pro:Desktop paola$ cd vfastronauts
Paolas-MacBook-Pro:vfastronauts paola$ ls
README.md
sample-doc
Paolas-MacBook-Pro:vfastronauts paola$ cd ..
Paolas-MacBook-Pro:Desktop paola$ 

Need Help? Tag me (@paolaperaza ) and ask away - I'll get a notification for it.

What

Well, your changes are considered live! The doc is up, and you can cross out that to-do.

How

Add a final comment to that GitHub issue and close it out. You're all set. Bonus points if you were able to point your commit to the GitHub issue the way I did in #13.

What

GitHub issue is closed, so let's close out that branch you created since it was specific to this project and to-do.

How

Instructions here: https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository.

Pro-Tip

To confirm, run $ git branch from your terminal (remember that branches are specific to github repos, so you have to be in vfastronauts repo from your terminal for it to show up or not).

Once you've closed all of these issues, you can CELLY!!

This document will have all of the top 10 moments from TC written as a list written in Markdown

What

Ok, so you've pushed up changes to your branch and put them up for review by creating a "PR" (Pull Request).

Now, let's merge those changes into master.

How

Typically this would warrant an actual feedback process (by adding someone else as the reviewer), but in this case - make yourself the reviewer. Feel free to add me.

If you don't see any conflicts, merge away!

Instructions here (you've seen this one before) 👉 https://guides.github.com/activities/hello-world/

Then, see your changes live in the overview of this repo!!! 🎉

What

Ok, so you've pushed up changes to your branch and put them up for review by creating a "PR" (Pull Request).

Now, let's merge those changes into master.

How

Typically this would warrant an actual feedback process (by adding someone else as the reviewer), but in this case - make yourself the reviewer. Feel free to add me.

If you don't see any conflicts, merge away!

Instructions here (you've seen this one before) 👉 https://guides.github.com/activities/hello-world/

Then, see your changes live in the homepage of this repo!!! 🎉

What

Ok, so your branch now has your latest work. Let's now push it up "for review" by creating a pull request.

Here, you're essentially saying "ok this is done, someone look it over. If it's good, merge to master!"

How

Instructions here 👉 https://guides.github.com/activities/hello-world/