Trigger Workflow preselects stale/unrelated branch instead of active workspace branch

Inizia dal comando dell’estensione o dalla UI che apre la finestra di dialogo per l’attivazione del workflow e traccia come viene risolta la branch/ref predefinita. Riproduci il caso con un branch attivo del workspace e un worktree collegato, quindi verifica che la finestra di dialogo preferisca l’HEAD del repository del workspace attivo e ricorra al fallback solo quando non è possibile determinare quell’HEAD.

Extension

GitHub Actions for VS Code

Summary

When triggering a workflow from VS Code, the branch/ref dropdown preselects an unrelated branch (often from a linked worktree or prior context) instead of the branch currently checked out in the active workspace folder.

Expected behavior

Default selected branch/ref should be the branch currently checked out in the active workspace repository.

Actual behavior

The dialog defaults to a different branch than the active workspace branch.

Repro (generic)

1. Create a repository with multiple branches.
2. Create at least one additional Git linked worktree with a different branch checked out.
3. In VS Code, open the original workspace folder on branch feature/current.
4. Use the extension command/UI to trigger a workflow manually.
5. Observe the preselected branch/ref in the trigger dialog.

Observed result

The preselected branch/ref is not feature/current; it appears to come from stale/cached/worktree context.

Notes

• Manually switching the branch in the dialog works, but the default is misleading and easy to miss.
• This can cause accidental workflow runs on the wrong branch.

Suggested fix

Prefer branch/ref resolution from the active workspace repository HEAD (and only fall back to cached/worktree-derived refs if workspace HEAD cannot be determined).