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

Reusable workflow links ignore `github-enterprise.uri` configuration

Open
#573 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript, vscode

Research direction

Start in src/workflow/languageServer.ts and trace how gitHubApiUrl from initializationOptions reaches reusable-workflow link generation. Reproduce the hover or click behavior with github-actions.use-enterprise enabled, then verify that enterprise links use the configured host while github.com links remain unchanged.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
When using github-actions.use-enterprise: true with a configured github-enterprise.uri (e.g. https://my-company.ghe.com), the links generated for reusable workflows in the uses: clause incorrectly point to github.com instead of the Enterprise instance.

To Reproduce
Steps to reproduce the behavior:

  1. Configure settings:
   \"github-enterprise.uri\": \"https://my-company.ghe.com\",
   \"github-actions.use-enterprise\": true
  1. Open a workflow file.
  2. Add a reusable workflow reference:
uses: my-org/shared-workflows/.github/workflows/workflow.yml@v1
  1. Hover or Click the link on the uses path.

Expected behavior
The link should open https://my-company.ghe.com/my-org/shared-workflows/blob/v1/.github/workflows/workflow.yml.

Actual behavior
The link opens https://github.com/my-org/shared-workflows/tree/v1/.github/workflows/workflow.yml.

Additional Context
The extension correctly passes gitHubApiUrl to the language server initializationOptions in src/workflow/languageServer.ts, but it appears the link generation logic in the language server defaults to github.com

Dominant language
TypeScript
Stars
661
Forks
214
PR merge metrics
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.