🩹 [Patch]: Move functionality of setting local environment variable #341
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.
Description
This pull request introduces a new function
Export-GitHubVariable
to the PowerShell module for handling exporting GitHub variables to the local environment, and updates the existingGet-GitHubVariable
function by removing theSetLocalEnvironment
parameter.New functionality:
Export-GitHubVariable
: Added theExport-GitHubVariable
function to export GitHub variables to the local environment with support for different scopes (Process, User, Machine).Updates to existing functionality:
Get-GitHubVariable
: Removed theSetLocalEnvironment
parameter and the associated logic to set environment variables locally.Testing:
tests/Variables.Tests.ps1
: Added multiple tests for theExport-GitHubVariable
function to ensure it correctly exports variables to the local environment. [1] [2] [3]Type of change
Checklist