mikepenz/action-junit-report

Unexpected input(s) 'comment'

Closed this issue · 7 comments

kjetilk-kontali commented

Hi,

I've added the GitHub Action as follows:

- name: Publish Test Report for Integration Tests
  uses: mikepenz/action-junit-report@v4
  if: always()
  with:
    report_paths: '.test-results/*.xml'
    detailed_summary: true
    comment: true
    include_passed: true

But when the action is run, I get the following warning:
Warning: Unexpected input(s) 'comment', valid inputs are ['token', 'github_token', 'report_paths', 'test_files_prefix', 'exclude_sources', 'suite_regex', 'annotate_only', 'check_annotations', 'update_check', 'check_name', 'commit', 'fail_on_failure', 'require_tests', 'require_passed_tests', 'include_passed', 'check_title_template', 'summary', 'check_retries', 'transformers', 'job_summary', 'detailed_summary', 'annotate_notice', 'follow_symlink', 'job_name', 'annotations_limit', 'truncate_stack_traces']

I can see from the docs (and the source code) that comment should be a valid input argument to the GH Action, so why am I getting this warning?

mikepenz commented

This feature is a v5 feature and is currently only available in the latest alphas:

kjetilk-kontali commented

Ah! That figures :)

PS. Might be an idea to mark the input args in the "Inputs" table with the version they're valid in? (e.g. ">5.0")

  • ❤️1
wmcnamee-coreweave commented

just ran into the same thing. Oops! Can I try out v5 some way?

PoqaTJ commented

Just ran into this as well, for both comment and updateComment. The docs should reflect what's available, not what's planned.

mikepenz commented

It's a common practice to have the default branch with the latest changes. Please refer to the respective tag you use for this tags documentation.