.github: workflows: add workflow to test fetch-configlet scripts#690
Merged
ee7 merged 6 commits intoexercism:mainfrom Oct 31, 2022
Merged
.github: workflows: add workflow to test fetch-configlet scripts#690ee7 merged 6 commits intoexercism:mainfrom
fetch-configlet scripts#690ee7 merged 6 commits intoexercism:mainfrom
Conversation
The `fetch-configlet.ps1` script currently always fetches the Windows release asset, so this workflow only tests that script on Windows. Closes: 121
Member
Author
ErikSchierboom
approved these changes
Oct 28, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fetch-configlet scripts were previously not tested during CI. Test them.
The
fetch-configlet.ps1script currently always fetches the Windows release asset:configlet/scripts/fetch-configlet.ps1
Line 16 in 7dd6784
so this workflow only tests that script on Windows. (Issue #361 tracks this low-priority problem).
Closes: #121