I generally don't like aliases being used (neither does PSScriptAnalyzer), but in this case, New-GitHubDeploymentEnvironment was writting to be able to behave as Set-GitHubDeploymentEnvironment as well, and we should be testing it the way that a user would likely be calling it.
Checklist
[x] You actually ran the code that you just wrote, especially if you did just "one last quick change".
[ ] Comment-based help added/updated, including examples.
[x] Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.
[ ] Relevant usage examples have been added/updated in USAGE.md.
Description
I generally don't like aliases being used (neither does PSScriptAnalyzer), but in this case,
New-GitHubDeploymentEnvironmentwas writting to be able to behave asSet-GitHubDeploymentEnvironmentas well, and we should be testing it the way that a user would likely be calling it.Checklist
[ ] Comment-based help added/updated, including examples.[ ] New/changed code adheres to our coding guidelines.[ ] Formatters were created for any new types being added.[ ] New/changed code continues to support the pipeline.[ ] Changes to the manifest file follow the manifest guidance.[ ] Relevant usage examples have been added/updated in USAGE.md.[ ] If desired, ensure your name is added to our Contributors list