github / github/vscode-github-actions

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

Ouverte
#420 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
bug
Langage dominant
TypeScript
Étoiles
660
Forks
213
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

**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`

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
typescript, vscode
Domaine
devtools
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.