redhat-developer / redhat-developer/vscode-yaml
Composite action arguments error
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
Hi, I use YAML + GitHub Workflow schema + composite actions
Expected Behavior
No errors
Current Behavior

Steps to Reproduce
Here are several snippets:
settings.json
{
"yaml.schemas": {
"https://json.schemastore.org/github-action.json": "**/actions/**/action.yml",
"https://json.schemastore.org/github-workflow.json": "**/workflows/**/*.yml"
}
}
workflow.yaml:
steps:
- name: Cache ${{ env.root }}
uses: ./.github/actions/each-devshell
with:
ROOT: ${{ env.root }}
SHELLS: ${{ env.root_devShells }}
action.yml:
inputs:
ROOT:
description: a dir for which this action should be run
required: true
SHELLS:
description: devShells names
required: true
Environment
- Windows
- Mac
- Linux
- other (please specify)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the settings.json schema mappings and reproduce the diagnostic using workflow.yaml and action.yml, focusing on the composite action's ROOT and SHELLS inputs. Done means the shown valid workflow and action metadata produce no argument errors under the GitHub Workflow schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode, yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100