haskell-actions / haskell-actions/setup
Expose GHCup binary location as action output
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 91
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
vscode-haskell needs direct access to ghcup to run its test successfully. Until recently, ghcup was always on $PATH and we could simply run ghcup install ... and install all the binaries that we needed. Additionally, the tests themselves also call ghcup install.
However, this seems to have changed recently for macos-latest: https://github.com/haskell/vscode-haskell/actions/runs/9015398738/job/24769933756?pr=1077
It looks like ghcup is not on the $PATH any more, but hidden somewhere in the hostedtoolcache.
One way to work around this for good, is to provide the path to ghcup as an action output, then we don't have to rely on ghcup to be on the $PATH, and can find it reliably.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by inspecting the action entry point and its existing output declarations, then reproduce the macos-latest behavior from the linked vscode-haskell run. Done means the action exposes a reliable ghcup executable path that downstream workflows can consume without relying on PATH; verify the affected workflow and tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100