Workflow dispatch fails for workflows in git submodules
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- git, github-actions, typescript, vscode
Research direction
Reproduce the failure with a parent repository containing a submodule workflow at .github/workflows/deploy.yml, using Trigger Run or the GitHub Actions explorer. Trace the workflow-dispatch path and how the opened file's repository is identified. Done means dispatching targets the submodule repository and the 404 no longer occurs.
Written by the indexing model from the issue text.
Description
Describe the bug
When attempting to trigger a GitHub Actions workflow located in a git submodule (e.g., host/.github/workflows/deploy.yml), the extension fails with a 404 "Not Found" error. The extension incorrectly attempts to dispatch the workflow to the parent repository instead of the submodule's separate GitHub repository.
To Reproduce
Steps to reproduce the behavior:
- Have a git repository with a submodule that has its own separate GitHub repository
- The submodule contains GitHub Actions workflows in
.github/workflows/ - Open the workflow file in VSCode
- Right-click and select "Trigger Run" or use the GitHub Actions explorer
- See error:
404 Not Foundor similar repository not found error
Expected behavior
The extension should:
- Detect that the workflow is located in a git submodule
- Identify the correct GitHub repository for that submodule
- Dispatch the workflow to the correct repository, not the parent
Screenshots
The error appears in the VSCode debug console when attempting to dispatch a workflow in the web submodule:
The extension is attempting to dispatch to the parent repository instead of the submodule's separate GitHub repository.
A user-facing error notification is displayed:
Note: Request IDs and repository names in the screenshot have been redacted for privacy.
Extension Version
v0.31.5
Additional context
This occurs in monorepo setups where submodules are separate GitHub repositories with their own workflows.
monorepo/ (Parent repo: github.com/owner/monorepo)
└── submodule/ (Submodule: github.com/owner/submodule)
└── .github/workflows/
└── deploy.yml ← Should dispatch to submodule repo
The extension's workflow dispatch logic needs to be aware of git submodules and route dispatch requests to the appropriate repository.
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
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.
More from github/vscode-github-actions
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/vscode-github-actions#627 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
github/vscode-github-actions#630 · 1 reaction ·
-
long work Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github/vscode-github-actions#628 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
github/vscode-github-actions#625 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
github/vscode-github-actions#621 · 3 comments ·
All issues in github/vscode-github-actions
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100