Skip to content

Fix constructing Gitlab object without authentication #900

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

Closed
wants to merge 1 commit into from

Conversation

jalr
Copy link

@jalr jalr commented Oct 7, 2019

unauthenticated access is broken since #876 was merged

fixes getting the error Only one of private_token, oauth_token or job_token should be defined when using no authentication method at all.

@max-wittig
Copy link
Member

Totally missed that. Thanks for the PR. Would you mind to use the commit conventions? So change to commit message to something like: fix: allow Gitlab object with auth

Thank you!

unauthenticated access is broken since python-gitlab#876 was merged
@jalr jalr force-pushed the allow-unauthenticated branch from a605589 to 19feb1e Compare October 7, 2019 18:09
@jalr
Copy link
Author

jalr commented Oct 7, 2019

No worries, sometimes it happens that you overlook something. I just noticed the issue today because my chat bot wasn't working anymore 😄
Just learned about the commit linter. Good idea to implement that! I hope that it passes now.

@@ -355,7 +355,7 @@ def _set_auth_info(self):
bool(arg)
for arg in [self.private_token, self.oauth_token, self.job_token]
)
!= 1
> 1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But this does exactly the reverse. It only works, if we have multiple parameters.

We should only check this condition, if the items are larger than 1

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.

2 participants