Unexpected input 'env_vars'
See original GitHub issueIssue Description
- name: Upload coverage to Codecov
uses: codecov/codecov-action@v1
with:
env_vars: OS,PYTHON
triggers warning Unexpected input 'env_vars', valid inputs are ['name', 'token', 'file', 'flags', 'fail_ci_if_error']
despite following the example of https://github.com/codecov/codecov-action#arguments
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Unexpected input(s) · Issue #10 · SpicyPizza/create-envfile
I wanted to use this action so I could create an .env file in the same directory as my app (where my sources...
Read more >Unexpected '/' in environment variables
I've tried unsetting BINREF (Sys.unset...) or setting to an empty string, or adding a double backslash when setting ( \\ ) but the...
Read more >Problems with Environment Variables
To check which environment variables are set, do the following (works for all versions of Windows): Open a DOS box (or a Command...
Read more >ENV02-J. Do not trust the values of environment variables
Compliant Solution. This compliant solution obtains the user name using the user.name system property. The Java Virtual Machine (JVM), upon initialization, ...
Read more >Env Variables and Modes
An env file for a specific mode (e.g. .env.production ) will take higher priority than a generic one (e.g. .env ). In addition,...
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 Free
Top 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
have same warning
env_vars
was only introduced byv0.1.7
. You could pin the version in the workflow: