-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expand on data extraction from github action runs for Coveralls #296
Conversation
Regarding tests ... it's not quite clear to me how to cover this. Happy for ideas. |
Codecov Report
@@ Coverage Diff @@
## master #296 +/- ##
==========================================
+ Coverage 81.90% 82.63% +0.72%
==========================================
Files 3 3
Lines 199 190 -9
==========================================
- Hits 163 157 -6
+ Misses 36 33 -3
Continue to review full report at Codecov.
|
Pull Request Test Coverage Report for Build 941
💛 - Coveralls |
Pull Request Test Coverage Report for Build 937
💛 - Coveralls |
3 similar comments
Pull Request Test Coverage Report for Build 937
💛 - Coveralls |
Pull Request Test Coverage Report for Build 937
💛 - Coveralls |
Pull Request Test Coverage Report for Build 937
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
It'd be nice to have some tests for this, just like we have for the other combinations of CI provider and Codecov/Coveralls in test/runtests.jl
.
But I personally wouldn't want to hold this PR hostage over this :-)
event_path = open(JSON.Parser.parse, ENV["GITHUB_EVENT_PATH"]) | ||
github_pr_info = get(event_path, "pull_request", Dict()) | ||
github_pr = get(github_pr_info, "number", "") | ||
isempty(github_pr) || (data["service_pull_request"] = github_pr) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooooh, that's nice, I wasn't aware of it, else I would have suggested it for PR #288 -- I wonder if perhaps you or @kyungminlee would be interested in adjusting the Codecov code path to also parse the GITHUB_EVENT_PATH
JSON. In general, we try to keep the Codecov and Coveralls support in sync (but I merged PR #288 anyway, because (a) I forgot 😨 and (b) honestly, I'd rather have something that works in now than to not have it at all because it's perfect...
Anyway: very nice 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure I can do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit tricky to use in general though, because for push builds you don't have that much info it seems (like I could not find how to e.g. extract the branch name in a quick search).
See https://docs.github.com/en/free-pro-team@latest/rest/reference/pulls for PRs and https://docs.github.com/en/free-pro-team@latest/rest/reference/repos#commits for push builds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess one then needs to combine techniques from PR #288 and this one... Ah well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, that's kind of what I did. Not sure that makes things a lot better, though.
👍 Thanks for merging. |
Based on the official docs.