Uh oh!
There was an error while loading. Please reload this page.
GitHubBranches: Add New/Remove-GitHubRepositoryBranch Functions - #200
GitHubBranches: Add New/Remove-GitHubRepositoryBranch Functions#200Simon Heather (X-Guardian) wants to merge 18 commits into
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Simon Heather (X-Guardian)
commented
Jun 5, 2020
Can we trigger the CI for this PR? |
Howard Wolosky (HowardWolosky)
commented
Jun 5, 2020
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Simon Heather (X-Guardian)
commented
Jun 5, 2020
The Context When the origin branch cannot be found tests are failing because I'm getting very different error objects back between PowerShell 5 and 7 when calling Adding some debug code, I can see that in PowerShell 5, and in PowerShell 7 Adding I think |
Howard Wolosky (HowardWolosky)
commented
Jun 6, 2020
I've opened #223 to track that problem. |
Simon Heather (X-Guardian)
commented
Jun 7, 2020
Can we trigger the CI for this PR? |
I've added the |
Simon Heather (X-Guardian)
commented
Jun 7, 2020
I've added temporary code to the |
Simon Heather (X-Guardian)
commented
Jun 12, 2020
Can we trigger the CI for this PR? |
Howard Wolosky (HowardWolosky)
commented
Jun 12, 2020
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Simon Heather (X-Guardian)
commented
Jun 12, 2020
Great to have a fast CI now! This PR is ready for final review. |
Howard Wolosky (HowardWolosky)
commented
Jun 12, 2020
Thanks for the encouragement/push to do the extra work to make the additional accounts to allow for the parallel processing!
Will get to the review this weekend or early next week. Thanks again for all your work here! |
Simon Heather (X-Guardian)
commented
Jun 18, 2020
Hi Howard Wolosky (@HowardWolosky), I've added pipeline support to these new functions. Can we trigger the CI for this PR? |
Howard Wolosky (HowardWolosky)
commented
Jun 18, 2020
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Simon Heather (X-Guardian)
commented
Jun 21, 2020
Can we trigger the CI for this PR? |
Howard Wolosky (HowardWolosky)
left a comment
There was a problem hiding this comment.
Finally had time to review this one in context to #97.
I think both PR's have a place in the module, but it would make sense for these two functions to be built on-top of New-GitHubReference/Remove-GitHubReference once that goes in.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| sha = $originBranch.commit.sha | ||
| } | ||
| $params = @{ |
There was a problem hiding this comment.
I think it probably makes more sense to allow #97 to go in, and then have this function be a wrapper on top of New-GitHubReference. You can still make this an intelligent helper that can automate retrieving the sha via an internal call to Get-GitHubRepositoryBranch when it hasn't been passed in manually or via the pipeline, but given that we'll want New-GitHubReference in the module anyway to be able to support tag references, it seems like it makes more sense to not duplicate the logic of forming a call to create new references across two functions. Same for Remove-*.
- Add New-GitHubRepositoryBranch and Remove-GitHubRepositoryBranch
- Add CBH Inputs - Fix CBH Outputs - Add PositionalBinding - Change Mandatory parameter order - Add Invocation parm to Write-InvocationLog - Fix getGitHubRepositoryBranchParms - Add temp code to handle diffs in exception object between PS5 & PS7 - Add ShouldProcess to Remove-GitHubRepositoryBranch
Simon Heather (X-Guardian)
commented
Jun 29, 2020
This PR is superseded by PR #256 |
Description
This PR adds the following functions to the
GitHubBranchesmodule:New-GitHubRepositoryBranchRemove-GitHubRepositoryBranchIssues Fixed
None
References
GitHub Repos API
Checklist
If desired, ensure your name is added to our Contributors list