Issue #192 explains that we want to create new repositories that contain examples that are organized in a new fashion and that adhere to a new naming convention.

Once all of these repositories exist, then it is possible to implement a new approach to integration testing. The idea would be that we can use a tool to clone all of the example repositories when we are testing new features of GatorGrader that are currently in a PR.

We would know that a repository like this one:

https://github.com/GatorEducator/java-assignment-starter-100-01

is a starter repository and thus, by design, the checks for this repo should fail, producing a non-zero exit code.

Alternatively, if we were running gradle grade in this repository:

https://github.com/GatorEducator/java-assignment-solution-100-01

then since it is a solution repository, all of the checks should pass, producing a zero exit code.

What I would like to have is a new approach to integration testing that makes it possible to run these checks automatically for all of the existing sample repositories that follow the new naming convention.