Repository navigation
GitHubRepositories: Add Get/Set/Remove GitHub Repository Team Permissions - #300
Howard Wolosky (HowardWolosky) merged 10 commits into
Conversation
|
Welcome back to the project, Simon Heather (@X-Guardian)! Apologies in the delay in getting these two PR's reviewed. Things have been a bit busy for me with my primary work. I promise to get to both of these PR's within the next few days though. Thanks again for your contributions! |
Howard Wolosky (HowardWolosky)
left a comment
There was a problem hiding this comment.
Thanks so much for this contribution, Simon Heather (@X-Guardian) (and my sincere apologies on the delayed review...I'll blame it on the holidays).
By and large this change looks great. The majority of the requests are just formatting the GitHub noun of "Team" to have a capital 'T' as opposed to a lower-case 't'.
The one design choice that I'm confused by however is the creation of your own return object in lieu of the GitHub object for Get-*. My inclination is to use the object that GitHub is returning, and add to it any additional information we think that the user might need....
|
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Regarding the |
Simon Heather (X-Guardian)
left a comment
There was a problem hiding this comment.
Howard Wolosky (@HowardWolosky), ready for the next review.
Howard Wolosky (HowardWolosky)
left a comment
There was a problem hiding this comment.
Update looks good. Thanks for the quick turnaround.
Two small nits that I can apply myself once the review is submitted.
Will kick off a new pipeline build for verification now.
Thanks again!
|
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Simon Heather (@X-Guardian) -- Can you resolve these conflicts locally to avoid the line ending changes that the web editor causes? |
|
Howard Wolosky (@HowardWolosky), conflicts resolved. Ready for the next review. |
|
Howard Wolosky (@HowardWolosky), any update on getting this PR merged? |
|
My apologies. Will get to this tomorrow. I had started looking at it earlier, but I think the rebase threw me off, as I was getting confused why tests were being deleted as part of the updates, and needed to devote more time to re-reviewing the whole thing. |
|
This is actually queued for review again this afternoon. Thanks for your patience. |
Howard Wolosky (HowardWolosky)
left a comment
There was a problem hiding this comment.
So very sorry for the delayed PR on this update. Holiday time has been pretty busy for me over here. Still, I should have communicated a bit better on this. Again, my apologies.
Your contributions, as always, are very much appreciated.
A few updates to this are being requested. Almost all of them have suggested changes that you can simply apply.
The main question that I have here (and I can't recall if I had the same concern the last time) is whether or not we need OrganizationName as an additional parameter to these methods, or if we can just re-use OwnerName as the OrganizationName as well. Do you know if it's possible for an organization's team to be given permission to an individual person's repo ? (I don't think you can).
| ValueFromPipelineByPropertyName, | ||
| ParameterSetName = 'TeamSlugUri')] | ||
| [ValidateNotNullOrEmpty()] | ||
| [string] $OrganizationName, |
There was a problem hiding this comment.
Same question as above.
There was a problem hiding this comment.
Done
Howard Wolosky (HowardWolosky)
left a comment
There was a problem hiding this comment.
All the updates here look good. Given our conversation around OrganizationName, I'll await a final update that removes OrganizationName and just has it reuse the OwnerName for both OwnerName and OrganizationName. Thanks again.
|
Howard Wolosky (@HowardWolosky), I've removed the OrganizationName parameter, so the PR is ready for the next review. |
Howard Wolosky (HowardWolosky)
left a comment
There was a problem hiding this comment.
This update looks good. Will kick off a pipeline and then merge upon completion.
Thanks!
|
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Howard Wolosky (@HowardWolosky), thankyou for merging this. Do you have any plans for releasing a new version? |
I'll get the next version released tomorrow or this weekend. |
Had a slight delay, but it's now published. Thanks again for your help here! |
|
No problem, thanks Howard. |
Description
This PR adds the following functions to the
GitHubRepositoriesmodule:Get-GitHubRepositoryTeamPermissionSet-GitHubRepositoryTeamPermissionRemove-GitHubRepositoryTeamPermissionIssues Fixed
Resolves #307
References
Checklist
If desired, ensure your name is added to our Contributors list