Madlibs Activity

For this activity, you will use what you've learned about git to work collaboratively as a classroom to fill out a couple Madlibs stories.

How To Setup This Activity

Form a group with your neighbors. You should choose one person whose computer you will use.
Make a Github account if you haven't already got one. This should be a personal account for the person whose computer is being used. We'll be using GitHub in our homework assignments this semester. You don't have to use identifying information when you create your account.
Fork the starter repository on Github. Forking means to make a copy of the code but attach it to your own Github repository so that you can make changes. Technically you are "cloning" the starter repo. GitHub calls this "forking" because they add some other bells and whistles on top. You should see a grey button at the top that says "fork"---that is what you want. If you need more information, look at https://help.github.com/articles/fork-a-repo/
Login to cloud9. You may have an invite to cloud9 from the instructor. Or, you may already have an account. Once you're in Cloud9, you'll want to link it to your GitHub account. Then, create a custom workspace, cloning from your forked repo. (Of course, you can do all these locally on your computer if you are advanced, instead of using Cloud9.)
Open the index.html file to see the app working on your computer.
Create new stories, verbs, nouns, adjectives, and adverbs! Or, just one of them---whatever you want. Checkout a new branch with a good name before you do your work. This will be a command like
```
git checkout -b kyle-new-verbs
```
Here, I named my branch "kyle-new-verbs". You should name yours something different, no spaces.
Take a look around at the files. Familiarize yourself where everything lives.
Create a new file. You can also edit existing files, but that will make our merging harder! If you want to make a new file of verbs, you might make a file at /js/verbs/my-new-file.js and in that file, add new verbs.

You should choose a name other than "my-new-file.js". You can use the command nano to create and edit files, or use the Cloud9 editor. You may also use the cloud9 editor, or a local text editor you have installed, like atom or vscode (my favorite).
Check your code works. Did you break the app? No? Great!
Commit your changes and share them

First, take a look at the status of your work
```
git status
```
It should show what files are new and what files are changed. Now, you want to add the new files, try the git add command. You'll need to supply a file name.

Once you've added your changes to the "staging area", you want to make a commit. This is a command like
```
git commit -m "Added some verbs for class"
```
Now, push your changes up to GitHub.
```
git push origin BRANCHNAME
```
where BRANCHNAME is the name of your branch.
Go to GitHub, find your fork and the new branch, then make a pull request

Pull requests let you tell others about changes you've pushed to a repository on GitHub. Once a pull request is sent, interested parties can review the set of changes, discuss potential modifications, and even push follow-up commits if necessary.

Click on the logo at right to get started. . Then, once you get to another page, click the blue link.

Finally, click the create button to checkout the commit. If you need extra help, check this out https://help.github.com/articles/using-pull-requests/ or just come see a TA.
The instructor will merge in everybody's work.

chenyusi/madlibs

Madlibs Activity

How To Setup This Activity