[v4] Using gcov argument results in warning

[jwillemsen]

I am using the gcov optional argument as described at https://github.com/codecov/codecov-action#arguments but that results in the warning below

2024-02-01T10:36:53.0226212Z ##[warning]Unexpected input(s) 'gcov', valid inputs are ['token', 'file', 'files', 'commit_parent', 'directory', 'dry_run', 'env_vars', 'exclude', 'fail_ci_if_error', 'flags', 'name', 'os', 'override_branch', 'override_build', 'override_commit', 'override_pr', 'plugin', 'plugins', 'root_dir', 'slug', 'url', 'verbose', 'version', 'working-directory']
2024-02-01T10:36:53.0238741Z ##[group]Run codecov/codecov-action@v4

codecov4warning.txt

[jwillemsen]

Upgrade PR RemedyIT/taox11#356

[jwillemsen]

Github action step

    - uses: codecov/codecov-action@v4
      with:
        gcov: true
        fail_ci_if_error: true 
        verbose: true # optional (default = false)
      env:
        CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

[radarhere]

After these comments were made, @thomasrockhu-codecov removed the 'gcov' argument from the README, and instead added

plugin | plugins to run. Options: xcode, gcov, pycoverage. The default behavior runs them all.

So is the solution to this to simply remove 'gcov: true', and rely on the default behaviour to run gcov?

[thomasrockhu-codecov]

@radarhere I'm sorry, I had meant to come back to this and reply, but I got caught in a few other things first.

Yes, the arguments in the README were outdated for v4. It was this issue that led me to that, so thank you. You should not need the gcov argument any longer. If I am mistaken and you run into issues, please let me know.

[thomasrockhu-codecov]

@jwillemsen the same should be true for you as well.

[jwillemsen]

Works without gcov now