fix the TeamClient.AddMembership(..) call #856
Merged
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.
While exploring some organizational automation with
octokit.net
I discovered that theTeamClient.AddMembership(..)
call passes anull
value into a parameter ofApiConnection.Put(..)
that fails on anOctokit.Ensure.ArgumentNotNull(..)
call.The GitHub API 3.0 Team docs state that the correct way to call the Add Team Member endpoint is to essentially pass an empty body:
My proposed fix (that I will submit shortly in this PR) is to have
ApiConnection.Put(..)
check for anull
body and respond by setting theContent-Length
header to zero as instructed, if that is possible, rather than throwing anArgumentNullExceptionValue
.Todo
Connection
object to add theContent-Length
header when thebody
isnull
Content-Length
header as that generated aSystem.InvalidOperationException: Misused header name.