reposense
Fail gracefully for large commits
In case a commit is huge (e.g., someone committed a huge library by accident), ensure RepoSense fails gracefully. Might need to check the following areas:
- during analysis
- chart view
- code view
How big is big? And can we really determine if the large commit is really by accident? I think we all seen the type of people who only push once the entire feature is complete?
Not sure if it's appropriate to tell users that their repository cannot be used for the report because it causes lag, even if they do not mind the lag.
The whole report should not crash (i.e., it should instead 'fail gracefully') even if the commit has 500 LKoC. Last time, a student committed a data file with 200 KLoC. In such cases, the rest of the report should work even if that commit/repo has to be omitted from the report.