🔧 Use GitHub-hosted runner for Pester tests#106
Merged
Conversation
J-MaFf
added
documentation
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
1 participant
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.
What does this PR do?
Updates the Pester test workflow to use GitHub-hosted runners instead of self-hosted runners, allowing tests to execute immediately.
Why are we doing this?
ubuntu-latestprovides immediate execution without setup overheadChanges
runs-onfrom[self-hosted, linux]toubuntu-latestTesting
The workflow will automatically run on the next PR or push to main/testing branches that modify Scripts/, Tests/, or Modules/ directories.