bradleyfalzon / gopherci / 177

63%

master: 61%

push

travis-ci

Write analysis to the database

This provides the foundations for a web view (discussed in #28),
so users can view the issues without relying on inline or issue
comments.

This also provides a mechanism to time how long the analysis is
taking as well as a per tool timing metric. This allows us to better
understand how much time different repositories or installations spend
checking.

We record which tools were executed, even if no issues were detected
so the user knows which checks passed. This will cause the analysis_tool
table to become very large over time.

Relates to #3.

112 of 112 new or added lines in 6 files covered. (100.0%)

635 of 1016 relevant lines covered (62.5%)

1.7 hits per line