Can now pass urls to commandline fairtally with progressbar

[jspaaks]

In this PR:

• Made fairtally accept urls via the commandline as arguments (Find how to pass list of URLs to fairtally #3)
• Added progressbar via tqdm (add progress bar #23)
• Added capturing of stdout and stderr, store for later reporting
• Added pre-commit githook (Add githook same as howfairis #15)
• Elevated rate limits already work (rate limiting / how to use apikeys to howfairis #9)
• Results are stored as array of object with keys (retain state of howfairis results for every URL #5):

  
  {
     url: string,
     badge: string,
     repository: bool,
     license: bool,
     registry: bool,
     citation: bool,
     checklist: bool,
     count: int,
     stdout: string,
     stderr: string
  }
  

• Added --html and --json options. If specified, fairtally will write to a json file or to an html file, respectively. html writing uses jinja2 templating and data/index.html.template.

For testing, you can put in your own URLs, but for convenience, the snippet below gives you the 10 URLs from the Research Software Directory which were changed most recently:

// Example to get a list of 10 most recently changed software items from Research Software Directory:
fetch("https://research-software.nl/api/software?limit=10&sort=updatedAt&direction=desc")
   .then((response) => {return response.json()})
   .then((data) => {
      console.log(data.map((x) => {
         return x.repositoryURLs.github[0]
      }))
   })

To test:

fairtally https://github.com/fair-software/howfairis https://gitlab.com/jspaaks/howfairis-livetest

Should show a progress bar and print results at the end

$ fairtally https://github.com/fair-software/howfairis https://gitlab.com/jspaaks/howfairis-livetest
fairtally progress: |██████████████████████                      | 1/2
currently checking https://gitlab.com/jspaaks/howfairis-livetest

If you have jq installed, you can pipe the results into it, like so:

fairtally <URL1> <URL2> <URL3> | jq '.'

or write to a json file:

fairtally --json results.json <URL1> <URL2> <URL3>

or write to an html file:

fairtally --html results.html <URL1> <URL2> <URL3>

Here's what that looks like in the browser:

[fdiblen]

Mention output formats in the help text

[jspaaks]

I split this up into a --html and a --json, each with separate help text; this also avoids having to run the tool twice if you happen to want both json and html output.

[jspaaks]

The pep8 linting check fails but that's because those rules aren't helping me write clean code. E.g. the linelength of 79, how function calls break over multiple lines, the fact that you cannot have an empty line after a function signature.

[sverhoeven]

Tests commands and pre-commit script ran correctly.
Spawned of some issues and left some inline comments for things that would otherwise never be done.

Great work.

[jspaaks]

committed the suggestions

[eriktks]

Testing html output results in an error message:

$ pip install .
...
$ fairtally --html results.html https://github.com/fair-software/howfairis https://gitlab.com/jspaaks/howfairis-livetest
...
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/erikt/anaconda3/envs/python37/lib/python3.7/site-packages/fairtally/data/index.html.template'

[jspaaks]

Testing html output results in an error message:

$ pip install .
...
$ fairtally --html results.html https://github.com/fair-software/howfairis https://gitlab.com/jspaaks/howfairis-livetest
...
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/erikt/anaconda3/envs/python37/lib/python3.7/site-packages/fairtally/data/index.html.template'

True, but will be fixed by #25. See also #26. Do you want me to fix it here as well? My guess is we're eventually going to merge #25 anyway right?

[eriktks]

No, the missing file issue does not need to be fixed here if it is already fixed in another issue. Thanks!

[fdiblen]

Works nicely. Thanks @jspaaks

[sverhoeven]

Thanks for reviewing, merged on behalve of @jspaaks