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 the Lab Repo Practice. It took about 30 minutes.
Reflect and summarize on your process for each TODO item :
First, I setup my 301 directory structure.
Next, I forked the Lab Repo Practice and worked the instructions from the README.
Finally, I submitted a Pull Request.
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"
[x] 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.
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
Single-line Summary
Today, I worked on the Lab Repo Practice. It took about 30 minutes.
Reflect and summarize on your process for each
TODOitem :Checklist (before submitting, fill in each set of square brackets with an 'x')
TODO:process above.