You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The commits generated by maven-semantic-release intentionally make commits that skip CI runs. Codecov seems to be looking at the commit as noted in the Travis environment variables (see this Travis build). Therefore, it only uploads a report for the commit that is a merge to master, not the release commit or post-release commit. The end result is that in the next PR made to master, a record of the last coverage report on master does not exist (#192 (comment)).
Expected behavior
Code coverage reports should be generated and uploaded for each commit to master.
Steps to reproduce the problem
Make a PR to merge to master.
Any special notes on configuration used
N/A
Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)
master branch
The text was updated successfully, but these errors were encountered:
Observed behavior
The commits generated by maven-semantic-release intentionally make commits that skip CI runs. Codecov seems to be looking at the commit as noted in the Travis environment variables (see this Travis build). Therefore, it only uploads a report for the commit that is a merge to master, not the release commit or post-release commit. The end result is that in the next PR made to master, a record of the last coverage report on master does not exist (#192 (comment)).
Expected behavior
Code coverage reports should be generated and uploaded for each commit to master.
Steps to reproduce the problem
Make a PR to merge to master.
Any special notes on configuration used
N/A
Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)
master branch
The text was updated successfully, but these errors were encountered: