Use PRIVATE-TOKEN header for passing the auth token#3
Merged
Conversation
Contributor
|
Hi, I'd like to merge this change, but I'm afraid it would break gitlab 4.x compatibility. The use of the header doesn't seem possible for those versions (according to the doc, I didn't look at the code). On the other hand, I have absolutely no idea if python-gitlab is used with gitlab 4.x... |
Contributor
|
gitlab v6 is out, v4 is getting old... Thanks for the patch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This moves the
private_tokenfield from out of the request url and into the request header.