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

Pinned workflows for folders other than the first in a Code Workspace don't appear in the status bar

Open
#420 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools

Research direction

Reproduce the issue in a multi-project Code Workspace using the GitHub Actions extension, then trace how pinned workflow paths are stored and resolved for the status bar. Done means qualified workflows from each project appear, while an unqualified .github/workflows/* path does nothing in a multi-project workspace.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
Clicking the pin & unpin buttons on workflows in a multi-project workspace add PROJECT-FOLDER-NAME/.github/workflows/WORKFLOW-NAME.yml to "github-actions.workflows.pinned.workflows", but in actuality, the only workflows that can actually show in the status bar are workflows for the first project in the workspace, and only when not qualified with the PROJECT-FOLDER-NAME

To Reproduce
Steps to reproduce the behavior:

  1. Open a new VSCode window and click File > Add Folder to Workspace, then choose a GitHub project with .github/workflows. Do it again for another GitHub project with workflows.
  2. In the GitHub Actions extension workflows list, pin workflows from both projects.
  3. No workflows will appear in the status bar.
  4. Open Workspace Settings (JSON), and for a workflow from the first project folder listed, remove the project name. IE, the path should be .github/workflows/WORKFLOW-NAME.yml.
  5. The workflow will appear in the status bar.

Expected behavior
Pinned workflows in a multi-project workspace should appear when they're qualified with the project name. The path .github/workflows/* in a multi-project workspace probably shouldn't resolve to anything and therefore should do nothing.

Extension Version
v0.27.0

Dominant language
TypeScript
Stars
661
Forks
214
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.