Hi, I'm using
https://codecov.io/bash script, copying some integration commands from existing projects and in one of them I noticed commands like this
lcov --gcov-tool=gcov-7 ...`
then (the bash script)
./codecov -f coverage.info -X gcov -x gcov-7
The confusing part is this disable
gcov, but run
Is that to ensure default non-versioned executable is not run but the preferred one is?
Is it possible that uses of
[ci skip] break codecov for pull requests?
Please, consider this:
git co master git ci -m "[ci skip]" git ci -m "[ci skip]" git co -b pr1 git ci -m "Fix bug" git push user pr1
Now, submit GitHub pull request based on branch
pr1 and observe
No coverage uploaded for pull request base
I recently started using the
projects feature to split up a mono-repository so that individual packages within the mono-repository have their coverage reported separately from one another. - https://docs.codecov.io/docs/commit-status#section-splitting-up-projects-example-
Is it possible to get coverage badges for each project? I'd like to place a badge on the README for each package, with the badge representing the coverage of that specific package, and not the entire mono-repository.
Errorstatus. Some stuck in
I do not believe CodeCov uses Gitter for support.
Their available support channels are documented here - https://codecov.io/support
I am not sure this is the right gitter room to ask, but Codecov has been leaving double comments on pull requests. For example: Valloric/ycmd#1177
Later when a PR gets updated, codecov updates only one of the two comments.
--flagsarg. Could this be preventing the new yaml from being loaded?