julien-wilson

[julienawilson]

Below is an example of what your pull request will look like each day before you and your partner fill it out together.
You may ignore any odd symbols you see here - these are markdown-specific characters.

Notes

• Any underscores you see will be replaced with your names and finally the time spent on the lab assignment. For today, fill in the blanks based on the content.
• Next you will document the approach you took solving each TODO item in the code base.
• Finally, you will check the boxes confirming proper PR practices on the resulting page. Try it out!

  Single-line Summary

Today, I worked on completing the test repo demo. It took about 30 minutes

Reflect and summarize on your process for each TODO item :

1. Following the Test Repo (Demo) instructions, I had no trouble with the first eight steps. This was my first time forking a repo, so it was a little unfamiliar, but not difficult to navigate.
2. The instruction in step 9 to "git push origin test-branch" was confusing because I had no such branch. I pushed to my julien-wilson branch created in step 5 and continued.
3. In GitHub I sent my pull request but later realized I hadn't satisfied all of the requirements. The PR title was not my name, and I had not filled out this PR form. I returned to finish these steps, with some trouble navigating the site and figuring out how to change these parts of the PR. I went through the process again by adding and then removing content in a test commit. This helped me familiarize myself with GitHub, and understand the process better.

   Checklist (before submitting, fill in each set of square brackets with an 'x')

   • [x] I have entered the Pull Request title in the format of "firstname-lastname"
   • [] This PR includes commits from both myself and my partner; e.g. We followed good pair programming practices by switching driver/navigator roles.
   • [x] There is no extraneous, unrelated code included in this PR.
   • [x] We have summarized our TODO: process above.