-
Notifications
You must be signed in to change notification settings - Fork 41
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
yamllint: command not found #37
Comments
I found the same problem when use act for local ci test.
|
I just looked at the action, it seems it doesn't actually install yamllint? I am a bit confused. |
I'm facing the same issue in a self hosted runner. I was under the impression this was a docker action (https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action), but it appears to be a composite action which only runs the Looks like versions prior to v3 might work. https://github.com/ibiqlik/action-yamllint/releases/tag/v3.0.0 Perhaps the action should verify that I will take a stab at this improvement. If it wouldn't be accepted, please let me know though so I don't waste my time. |
I was able to fork this repository and fix it for myself by modifying using: 'composite'
steps:
- run: ${{ github.action_path }}/entrypoint.sh
shell: bash
env:
INPUT_FILE_OR_DIR: ${{ inputs.file_or_dir }}
INPUT_CONFIG_FILE: ${{ inputs.config_file }}
INPUT_CONFIG_DATA: ${{ inputs.config_data }}
INPUT_FORMAT: ${{ inputs.format }}
INPUT_STRICT: ${{ inputs.strict }} with using: 'docker'
image: 'Dockerfile' If this has no other unwanted side effects, I would like to see this fixed upstream. |
Good thinking! The only problem I can see is that this builds the image each time. |
I ended up installing into a |
From what I'm reading, |
Running your action with
act
currently produces:This is how I use it:
The text was updated successfully, but these errors were encountered: