Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHubBranches: Add New/Remove-GitHubRepositoryBranch Functions #200
GitHubBranches: Add New/Remove-GitHubRepositoryBranch Functions #200
Changes from all commits
7071089
113bab1
ee023f8
9ddd6ad
5c0c55c
0059036
1fcda48
7abab89
23a3839
32dec0c
7a4ba22
8ae5dbf
e346fcc
8f5404e
b3e50a7
0b3d1bd
e2f0b0e
d89afdd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 thesha
via an internal call toGet-GitHubRepositoryBranch
when it hasn't been passed in manually or via the pipeline, but given that we'll wantNew-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 forRemove-*
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding
GitHub.Branch
to this doesn't feel right. You're getting back a Reference object which has a different set of properties vs a branch object. That would affect.OUTPUTS
andOutputType
as well.