Add support for GitHub Actions

[davidanthoff]

Fixes #232.

[codecov-io]

Codecov Report

Merging #233 into master will decrease coverage by 0.41%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #233      +/-   ##
==========================================
- Coverage   90.53%   90.11%   -0.42%     
==========================================
  Files           6        6              
  Lines         338      344       +6     
==========================================
+ Hits          306      310       +4     
- Misses         32       34       +2

Impacted Files	Coverage Δ
src/codecovio.jl	86.15% <50%> (-1.15%)	⬇️
src/coveralls.jl	79.1% <50%> (-0.9%)	⬇️
src/lcov.jl	96.07% <0%> (-1.93%)	⬇️
src/Coverage.jl	98.13% <0%> (+0.96%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca1883f...dec5ee0. Read the comment docs.

[davidanthoff]

Ready for review. Might be a good idea to squash things before a merge, there are some false starts in the commit history.

[DilumAluthge]

Bump.

[DilumAluthge]

Bump. @davidanthoff What's the status of this PR?

[davidanthoff]

From my end it is ready for review and merging.

[DilumAluthge]

Do you know who the current maintainers of Coverage.jl are? We could ping them on GitHub and/or Slack.

[vtjnash]

add branch = GITHUB_REF? and maybe pr?? = GITHUB_EVENT_NAME?

[davidanthoff]

I think I had the branch= story in there before, and for some reason removed it, I think maybe it didn't work? I can't remember...

I don't have time right now to make more changes and test them, so I would suggest we merge the current version (because that certainly works), and then if someone else has more time to add more info and test out whether that works we can do it in a follow up PR?

[davidanthoff]

Great! Can we also tag a new release?