-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to input some options #33
Comments
I believe the cause of this problem is as follows. README.md says:
When you set up like this, GitHub Actions will look for the In that case, the old action will be referenced, so it is an expected behaviour that there would be the parameters that don't defined.
inputs:
command:
description: run or list
required: true
default: 'run'
path_pattern:
description: Path pattern
required: true
debug:
description: Filter runbooks to be executed
required: false
default: false
fail-fast:
description: Fail fast mode
required: false
default: false
skip-test:
description: Skip test mode
required: false
default: false I assume this also aligns with the warning in @asayamakk 's test flow.
To avoid this, you need to specify another ref but the problem is #32 need to be merged in order to use the version tag larger than |
https://github.com/k1LoW/runn?tab=readme-ov-file#scope A scopes option has been added to runn. |
It was already implemented. @asayamakk |
When passing the following options mentioned in the README to 'with', it results in "Unexpected input(s)" and does not function as expected:
'verbose', 'enable-run-exec-scope'
There may be other options that also cannot be used.
Here is the YAML for GitHub Actions to reproduce this issue:
runn yaml (not necessarily required)
You can also check this in the GitHub Actions Log of this repository
https://github.com/asayamakk/runn-action/actions/runs/10262294125/job/28391670470#step:4:1
(Note that login or permissions may be required to view, if unable to access it, I will invite you)
How should I pass the
enable-run-exec-scope
as described in the README?The text was updated successfully, but these errors were encountered: