Feature/GitHub codespaces organization
Description
Add outstanding support for Codespaces organizations and Codespaces machines.
Issues Fixed
- #406
References
- [x] Manage access control for organization codespaces
- [x] Add users to Codespaces billing for an organization
- [x] Removes users from Codespaces billing for an organization
- [x] Stop a codespace for an organization user
Checklist
- [x] You actually ran the code that you just wrote, especially if you did just "one last quick change".
- [x] Comment-based help added/updated, including examples.
- [x] Static analysis is reporting back clean.
- [x] New/changed code adheres to our coding guidelines.
- [x] Formatters were created for any new types being added.
- [x] New/changed code continues to support the pipeline.
- [x] Changes to the manifest file follow the manifest guidance.
- [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.
- [x] Relevant usage examples have been added/updated in USAGE.md.
- [x] If desired, ensure your name is added to our Contributors list
Added a couple of tests. But, I'm not sure how best to go about testing the following, for which I am open to suggestions:
- Add-GitHubCodespaceUser
- Remove-GitHubCodespaceUser
- Set-GitHubCodespaceVisibility
Added tests, FWIW. They work in my test organization, but I cannot guarantee they will work in yours.
- Add-GitHubCodespaceUser
- Remove-GitHubCodespaceUser
- Set-GitHubCodespaceVisibility
@HowardWolosky: Please review.
Thanks @vercellone - Will work on finding some time in the coming week or so to get through this contribution. Much appreciated, and thanks for your patience here.
Nudge @HowardWolosky
Please review, @HowardWolosky.
TypeName assertions resolved. Any other feedback, @HowardWolosky?
/azp run PowerShellForGitHub-CI
Please review again, @HowardWolosky.
@HowardWolosky 8 months!? Your resource management policy seems a bit biased.
@HowardWolosky?