Closed miroslavpojer closed 1 month ago
Oh wait a minute, this is almost an exact copy of https://github.com/AbsaOSS/balta/pull/10/files. I propose to repoint this PR to that branch then, not to master.
Oh wait a minute, this is almost an exact copy of https://github.com/AbsaOSS/balta/pull/10/files. I propose to repoint this PR to that branch then, not to master.
Yeah, @miroslavpojer took my branch, added JaCoco support and created a PR. But directed it to master
which I kind of missed. Therefore it's confusing.
Oh wait a minute, this is almost an exact copy of https://github.com/AbsaOSS/balta/pull/10/files. I propose to repoint this PR to that branch then, not to master.
Yeah, @miroslavpojer took my branch, added JaCoco support and created a PR. But directed it to
master
which I kind of missed. Therefore it's confusing.
Hi, sorry for that. I have repointed it to from master.
It would be good to document some usages / supported types etc into README, but otherwise really good work, I like the
Either
approach you chose, apart from many other things :)
Documented in README.md in commit f89709484446701ae85540a6b3a07ccdda696919,
Actually I noticed that the GH Pipeline definition for adding code coverage into PRs is missing.
LGTM otherwise
You are right, I will add it. @lsulak, @benedeki What do you prefer?
I would follow the second option as depends on the job on build.yml. I have prepared it already.
File | Coverage [0%] | :x: |
---|---|---|
SetterFnc.scala | 0% | :x: |
Total Project Coverage | 0% | :green_apple: |
---|
Overall Project | 30.04% | :green_apple: |
---|
There is no coverage information present for the Files changed
JaCoCo introduced into project.
Closes #11