Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to resolve action `$/.github/actions/...`

Open Beginner friendly
  • Is something wrong?
#638 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
79/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript, vscode
Domain
devtools, tooling

Research direction

Find the extension's validation path for uses: values and compare how it resolves ./<path> with the reported $/<path> form. Start by searching the repository for the invalid-uses-format diagnostic and its tests. Update the relevant validation so $/<path> resolves like ./<path>, then confirm the reported example with the existing tests.

Written by the indexing model from the issue text.

Description

GitHub's changelog added self-repository syntax for uses:: a value starting with $/ refers to the workflow's own repository at the running commit, with no checkout needed. It is documented to work everywhere ./ works.
https://github.blog/changelog/2026-07-30-reference-same-repository-actions-with-self-repository-syntax/

The extension accepts ./ but reports an error for the equivalent $/.

Before (./): no error

steps:
  - uses: ./.github/actions/my-action

After ($/): error

steps:
  - uses: $/.github/actions/my-action

Unable to resolve action `$/.github/actions/my-action`, no 'action.yml' or 'action.yaml' found in '.github/actions/my-action' (invalid-uses-format)

action.yml exists at .github/actions/my-action/, and the workflow runs correctly on GitHub with the $/ form. Only the editor validation is wrong.

Expected: $/<path> resolves the same way as ./<path>, with no error.

Dominant language
TypeScript
Stars
665
Forks
221
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.