Taylor is on the right track, and Kelsey probably could have posted her comment as a separate answer, so that it could be voted up / selected separately.
First of all, the key purpose of this lab is *not* to merely complete it, but rather to understand what is going on with git/GitHub.
If you completed Part I of the lab on a lab computer in 204, what is the situation? Let's recap. In Part I, you started off by creating a new repo (repository) on GitHub, which just contained a README.md file. You cloned that repository onto the "H:" network drive using the local lab machine you were working on, and edited some files, and committed those changes to the local repository. Eventually you *pushed* those changes back to GitHub. So by the end of Part I, GitHub has an up-to-date copy of everything in the local repository on your H: drive.
Thus, it is INDEED a good time to switch computers. (If you wanted to switch part-way through part I, before you had done the PUSH, then that would be a problem, because the changes you'd made on your H: drive repo wouldn't be reflected in the online GitHub repository.)
Once you now switch to working on your own computer, you'll need to make a new local repository. To do this, you'll want to "clone" the GitHub repo onto your own computer, which means:
Follow steps 1-4 of Part I, just like Kelsey said! (Except, because you're doing it on your own computer, rather than a lab machine, you'll need to store the repository somewhere else besides the H: drive, so perhaps use "C:" instead of "H:" anywhere that comes up.
Note that after performing steps 1-4 this second time around, your repo will already have the emu.txt file and your other changes.
So, in fact, you *couldn't* just go back and restart the lab from the very beginning (unless you delete the TestRepo repository on GitHub, and recreate it again...)
Hope that helps...