NOTES

Auto-detect scenario where semi-logarithmic plotting would help
(large peak in time window, too little resolution in most part of
the time window) -- or, always show semi-logarithmic view?

Add credits to README:
 pandoc
 altair
 vega
 carbonplan styles
 ...

Write out stargazer/fork time series
https://github.com/jgehrcke/github-repo-stats/blob/ab8879f76be7d54c940ba6bdcc6dbf55527aa3b9/analyze.py#L1080

Use https://github.com/arzzen/git-quick-stats

Switch to using https://github.com/jd/tenacity

Note here when done:
https://stackoverflow.com/questions/12850864/is-it-possible-to-track-views-and-clones-of-my-github-repositories

Bake chromedriver into docker image

Collect and visualize Forks-over-time

The HTML view shows detail about referrers
graphs/traffic?referrer=govdata.de
Note sure if this can be seen from the API. Tried things.
Could always scrape this if the API does not provide that level of detail.


https://discuss.newrelic.com/t/lambda-function-to-send-your-github-traffic-statistics-to-new-relic-insights/104121

Maybe do something like
https://pypi.org/project/github-traffic-stats
but focus on GH actions first

Add commentary to what the plots show.

For stargazers, link to
https://opensource.stackexchange.com/a/5114/21503


HTML report: also render as PDF via e.g.
https://github.com/westmonroe/pdf-puppeteer
https://github.com/fraserxu/electron-pdf/ seems pretty broken (tried it)
https://www.npmjs.com/package/html5-to-pdf: tried, but didn't work
https://github.com/arachnys/athenapdf
https://github.com/Szpadel/chrome-headless-render-pdf
https://github.com/westy92/html-pdf-chrome
also see appendix in
https://medium.com/compass-true-north/go-service-to-convert-web-pages-to-pdf-using-headless-chrome-5fd9ffbae1af

For storage, consider this:
Setup, management etc can all be vastly simplyfied when storing in a branch
in the repo that this action is set up in
/snapshots
/reports
    /2020-12-xx
    /2020-12-xx
/latest-report
/README.md

Explore using https://github.com/nektos/act for more confident testing (so that we get get a stronger signal from CI, almost as if we were to run manually in a test repo)