Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add CustomHeaders member to GitPushOptions #1233

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

Merged
merged 1 commit into from
Nov 12, 2015

Conversation

pearswj
Copy link

@pearswj pearswj commented Nov 12, 2015

This adds CustomHeaders member to GitPushOptions to match underlying c struct for marshalling. Fixes #1217 (error when pushing to private repo).

Supersedes #1218@golsby asked me to tidy things up and resubmit as per @nulltoken's comments.

Fix libgit2#1217
Matches underlying c struct for marshalling
@pearswj pearswj mentioned this pull request Nov 12, 2015
@nulltoken nulltoken added this to the v0.22 milestone Nov 12, 2015
nulltoken added a commit that referenced this pull request Nov 12, 2015
Add CustomHeaders member to GitPushOptions
@nulltoken nulltoken merged commit f8c944b into libgit2:vNext Nov 12, 2015
@nulltoken
Copy link
Member

Awesome! Many thanks to @golsby and you ✨

@golsby
Copy link
Contributor

golsby commented Nov 13, 2015

You're welcome! I'm happy to help. Fortunately, I've got @pearswj as a colleague who has much better git-fu than me to do the rebasing and commit squashing to clean up your commit log.

@akanieski
Copy link

I notice this was added - but I don't see a parallel to CustomHeaders in PushOptions.cs so how does it make it's way to the Proxy?

@TackyTortoise
Copy link

These custom headers are still not exposed to the end user since they are not included in PushOptions, unless I'm missing a different way to do this? There seems to be an open PR with a fix though: #2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants