Submitting Your Assignment
You're now ready to submit your first CS 70 assignment!
What Counts as Submitting
Your work lives in your repository, and pushing keeps it safe—but pushing is not submitting. You will often push work that isn't finished, and we need to know which version you actually want us to look at.
So submitting is one command, run on the CS 70 server from inside your homework directory:
cs70-submit
That records the current state of your work as your submission. It tells you what it did, and if something is wrong it tells you that instead.
What if I keep working afterwards?
Go ahead—submitting takes a snapshot, so carrying on doesn't disturb what you already submitted.
And if I improve it and want the new version?
Run
cs70-submitagain. You can submit as many times as you like before the deadline, and the last one is the one we grade.
Before You Submit
cs70-submit will check these for you and complain if they're not true, but
you can save yourself a round trip:
- Everything is committed. Run
git status; it should tell you there is nothing to commit and your working tree is clean. - Everything is pushed. If you're not sure,
git pushagain—it is safe to push when there is nothing to push.
It says I have uncommitted changes and it won't submit.
That's the check doing its job: a file you edited but never committed is not part of your work as far as git is concerned, and would not have been submitted.
git addthe files you meant to change,git committhem, then runcs70-submitagain.
How to Tell It Worked
This is the part that matters, and it's why submitting is a command rather
than a checkbox: cs70-submit tells you. It prints a confirmation saying
what it submitted and when.
If you don't see that confirmation, you have not submitted, no matter what else happened. Read what it printed instead—it will say what went wrong—and if you can't make sense of it, bring it to us in lab, at office hours, or at grutoring hours. Bring the message it gave you.
(When logged in, completion status appears here.)