Provide complete, TA repo that passes tests

[frozenfrank]

Overview

TAs want to have a communal repo of code that passes the tests. This increases our ability to validate that changes to testing code work.

Discussion

This goal is made difficult because the autograder currently accepts only public repos. Adding a public "answer" repo to this organization would be very bad. We could try to give the autograder access to a private repo. Storing the repo in a different organization makes it difficult/non-sustainable for general TA use.

[mewilker]

I missed a memo, how come we want a communal repo? What's wrong with our implementations?

[frozenfrank]

@mewilker Our implementations are great. With the regular updates and changes to the course/autograder, it would be nice to have an officially maintained repo with a branch for each phase that is known to pass all the tests. Developers could then reliably use this repo to test changes to the autograder or pass-off tests etc... This would also allow us to collaboratively update the repo as necessary with any changes in one location rather than requiring each TA to implement it from scratch.

Whether or not this issue comes to fruition (it's currently only a proposal/request, and it may be ignored or never implemented), TAs will of course always be able to continue testing any repo URL in the AutoGrader via the admin feature.

[ZakkeryDaRebel]

I mean, I don't think this is a necessary thing. But if it was something we wanted to do, we could create a GitHub account with the TA google account, and make the communal repo there, and have the github tag be something all TAs can remember and use to test if wanted. But ultimately, I feel like just using our own implementation is just fine, I don't see a communal repo as necessary.