The RampUp metric calculation and execution is very, very strange. There are two different modules that implement the 'analyze README' logic. One clones the entire repository, then looks only at the README to check for specific headers. The other pulls the README via the API and does the same thing. This is leading to inconsistent RampUp scores each time a specific package is evaluated, and is just generally error prone code.
Determine where the inconsistencies are coming from and apply a fix.
Delete testingRepo or eliminate the 'clone repo' functionality all together (Phase 2 doesn't require a metric to be evaluated without the use of the GitHub API).
There shouldn't be two different files doing the same thing.
The RampUp metric calculation and execution is very, very strange. There are two different modules that implement the 'analyze README' logic. One clones the entire repository, then looks only at the README to check for specific headers. The other pulls the README via the API and does the same thing. This is leading to inconsistent RampUp scores each time a specific package is evaluated, and is just generally error prone code.