Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fetch-configlet.ps1: don't require Windows #361

Open
ee7 opened this issue Jun 17, 2021 · 0 comments
Open

fetch-configlet.ps1: don't require Windows #361

ee7 opened this issue Jun 17, 2021 · 0 comments
Labels
kind: feature User-facing enhancement

Comments

@ee7
Copy link
Member

ee7 commented Jun 17, 2021

From exercism/problem-specifications#1799 (comment):

In the future, we could consider modifying the PowerShell script to also download the binaries for non-Windows OS'es (PowerShell is cross-platform nowadays).

This seems like a good idea - it's more complex to explain to users that the bash script works on macOS/Linux/Windows, but the PowerShell script is Windows-only.

Might be a good idea to test these scripts in CI first, see: #121

@ee7 ee7 added the kind: feature User-facing enhancement label May 15, 2022
ee7 added a commit that referenced this issue Oct 31, 2022
Before this commit, the fetch-configlet scripts weren't tested in CI.
Add a workflow to test them.

The `fetch-configlet.ps1` script currently always fetches the Windows
release asset, so this workflow only tests that script on Windows.

Closes: #121
Refs: #361
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: feature User-facing enhancement
Projects
None yet
Development

No branches or pull requests

1 participant