Feature/GitHub codespaces organization

[Jason Vercellone (vercellone)]

Description

Add outstanding support for Codespaces organizations and Codespaces machines.

Issues Fixed

• API Coverage: Add Support for Codespaces #406

References

Codespaces/organizations

• Manage access control for organization codespaces
• Add users to Codespaces billing for an organization
• Removes users from Codespaces billing for an organization
• Stop a codespace for an organization user

Codespaces/machines

• List available machine types for a repository
• List machine types for a codespace

Checklist

• 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.
• Static analysis is reporting back clean.
• 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.
• 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.
• If desired, ensure your name is added to our Contributors list

[Jason Vercellone (vercellone)]

Please review, Howard Wolosky (@HowardWolosky).

[Jason Vercellone (vercellone)]

TypeName assertions resolved. Any other feedback, Howard Wolosky (@HowardWolosky)?

[Howard Wolosky (HowardWolosky)]

Thanks for those updates. Looks just about there. I'll kick off a validation run to see if I missed anything else.

[Howard Wolosky (HowardWolosky)]

My preference here would be to avoid ambiguous code. As a code reader, it took too much time for me to look at what's here and parse out what might be happening. A comment could probably address that, but even better would simply be having the code be declarative on intention. In this specific scenario, this could be resolved by augmenting the $CodespaceName declaration to be part of two different parametersets, and then having the default one be one that's actually defined.

        [Parameter(
            Mandatory,
            ValueFromPipeline,
            ValueFromPipelineByPropertyName,
            ParameterSetName = 'Organization')]
        [Parameter(
            Mandatory,
            ValueFromPipeline,
            ValueFromPipelineByPropertyName,
            ParameterSetName = 'AuthenticatedUser')]
        [string] $CodespaceName,

[Howard Wolosky (HowardWolosky)]

/azp run PowerShellForGitHub-CI

[Jason Vercellone (vercellone)]

Please review again, Howard Wolosky (@HowardWolosky).

[Jason Vercellone (vercellone)]

Howard Wolosky (@HowardWolosky) 8 months!? Your resource management policy seems a bit biased.

[Jason Vercellone (vercellone)]

Howard Wolosky (@HowardWolosky)?

[Jason Vercellone (vercellone)]

Am I missing something here? How can I move this PR forward? Should I submit a new PR?