Skip to content
Snippets Groups Projects
Commit fded622e authored by Stockton Jenkins's avatar Stockton Jenkins
Browse files

Edit projects.md

parent cb8669a2
No related branches found
No related tags found
No related merge requests found
......@@ -175,7 +175,7 @@ pip install -r requirements.txt
Whenever you push to `main`, we run `autobadger` on your `main` branch. We then push our results to your repository under `Issues`.
This issue will contain the contents of `autobadger` as well as some other metadata and notes. This will most likely be your project's final grade, though we do manual reviews of your code as well to check against cheating and hardcoding. We also take the highest grade of all your submissions. In other words, if you get 100 on a GitLab issue, then you are done! :)
This issue will contain the contents of `autobadger` as well as some other metadata and notes. This will almost always be your project's final grade, though we do manual reviews of your code as well to check against cheating and hardcoding. We also take the highest grade of all your submissions. In other words, if you get 100 on a GitLab issue, then you are done! :)
### IMPORTANT!
......@@ -184,10 +184,12 @@ This issue will contain the contents of `autobadger` as well as some other metad
1. You receive a GitLab issue (within a reasonable amount of time, i.e. an hour, but normally much shorter than that)
2. The results you see align with what you expect.
If there is an issue with (1) or (2), double check your code, give it some time before you push again or [rerun your GitLab pipeline](https://piazza.com/class/m64hzy9v23v398/post/85). If the issue is not resolved, then reach out to your [TA](https://docs.google.com/spreadsheets/d/1HwI0o3IE97AWe_P_sKRPrUITPPGEdvsLzfEKcrP8NrU/edit?usp=sharing) or visit us in office hours.
If there is an issue with (1) or (2), double check your code, give it some time before you push again or [rerun your GitLab pipeline](https://piazza.com/class/m64hzy9v23v398/post/85). If the issue is not resolved after a few attempts, then reach out to your [TA](https://docs.google.com/spreadsheets/d/1HwI0o3IE97AWe_P_sKRPrUITPPGEdvsLzfEKcrP8NrU/edit?usp=sharing) or visit us in office hours.
As such, it is _highly recommended_ to start early, push often, and not wait till the minutes before the deadline to submit! Give yourself a buffer against an unexpected issues.
Since it is your responsibility to verify your GitLab issue (and your submission), we will not accept revision requests due to you not checking the status of your GitLab issues beforehand.
> **NOTE**: Be carefull not to push after the deadline unless your intention is to submit late (see policy below).
### Miscellaneous
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment