Warning: Unexpected input(s) 'fail_on_unmatched_files'
See original GitHub issueGetting a warning when using fail_on_unmatched_files
Warning: Unexpected input(s) 'fail_on_unmatched_files', valid inputs are ['body', 'body_path', 'name', 'tag_name', 'draft', 'prerelease', 'files']
https://github.com/visualon/jenkins-gitea-plugin/runs/2057690081?check_suite_focus=true
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Warning: Unexpected input(s) ..., valid inputs are [...] in GitHub ...
After github action running I got this warning:.
Read more >Unexpected Input · FME Desktop Basic Training 2016
Unexpected input is reported only for file datasets; databases do not cause ... it's more likely to be a problem and the unexpected...
Read more >R Error: Unexpected Input in X (2 Examples) - Statistics Globe
This article illustrates how to deal with the error message “unexpected input in X” in the R programming language. The page contains these...
Read more >Hi, at github action state it shows Warning - Medium
Warning : Unexpected input(s) 'host', 'key', 'username', 'scripts', valid inputs are ['repository', 'ref', 'token', 'clean', 'submodules', ...
Read more >Handling Unexpected Inputs in Voice Design
Expect The Unexpected - Handling Unpredicted Inputs. Dylan Zwick. Oct 18, 2018. 3 min read. What should your voice application do when it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for dragging my feet on this I got caught up in some family business.
I’m try to cut a release this weekend. I just have to make sure everything that’s changed is captured in the change log so I don’t break existing users workflows
We definitely need a new release