Add service_number for github actions

[bboe]

Using this coveralls command for parallel github action requires passing a unique service_number field (allowing the job to auto increment).

Using the sha syntax is consistent with how the Coveralls github action names the build so that it can be reported successfully:
https://github.com/coverallsapp/github-action/blob/master/lib/run.js#L43

Here's the commit I tested this against to verify parallel builds group successfully:
praw-dev/prawtools@bb0e00b

[TheKevJames]

@bboe thanks for contributing this -- much appreciated! I especially appreciate the link to the test run; thanks!

Looks like there's a few test failures and pieces I need to update in the docs/tests for this change, so I've gone ahead and updated your PR to include those changes and merged that to master.

I have to do a bit of clean-up work pre-merge since someone went and deprecated Python 2.7 and 3.4 while my back was turned, but I'll get this released as a new version shortly!

[bboe]

Happy to help. Thanks for merging!

[TimoRoth]

I think the coveralls action changed its behaviour here, and now uses GITHUB_RUN_ID to identify the builds?
At least I am unable to finish a parallel build using this package with it:

Error: Parallel webhook error:Error: {"error":"No build matching CI build number 129178104 found"}, {"error":"No build matching CI build number 129178104 found"}

I am for now working around this by doing this:

GITHUB_SHA="$GITHUB_RUN_ID" GITHUB_REF="" coveralls

[MarvinT]

@TimoRoth
I'm able to get it to run using

      - name: Coveralls
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          coveralls

if I pip install git+https://github.com/TimoRoth/coveralls-python.git until #227 is pulled in.

An example configuration is here: greenelab/ponyo#11
but its complicated a bit by using a conda installation to deal with R dependencies