Problem with .pep8speaks.yml and private repositories about pep8speaks HOT 6 CLOSED

1. Make sure the indentations are properly working. Please send it to me, and I might verify.
2. Are you using the BOT_USERNAME and BOT_PASSWORD os vars? Tokens don't seem to work here.
3. .pep8speaks.yml file is taken from the branch of the PR (and not the repository). So, make sure your PR is rebased/updated with the file.

I can only help with these suggestions as of now.

from pep8speaks.

@OrkoHunter thanks for suggestions

1. I use this configuration example.
2. Yes, recheck them.
3. I consider it.
   but I think problem is here because we use organisation and url to .pep8speaks.yml is https://raw.githubusercontent.com/{organisation}/{repository}/{sha}/{file} without user

also I can make curl request to get raw file only with 'Authorization: token {token}' in header. Are you sure that you need to make request with BOT_USERNAME and BOT_PASSWORD?

from pep8speaks.

but I think problem is here because we use organisation and url to

Doesn't this add the user credentials as auth ?

from pep8speaks.

@OrkoHunter problem is not in user credentials - problem in url.
Here my fix what works with my public and private repo.

I think here can be used repo.full_name from github webhook(url). What you think?

Doesn't this add the user credentials as auth ?

I mean what the reason to use auth if you add auth token
this not related to this issue

from pep8speaks.

I mean what the reason to use auth if you add auth token

I think this happened because the user token I had generated initially (for working with public repositories) was with minimal permissions and hence I had to add the auth for working with private repositories. Of Course it can work with one only.

from pep8speaks.

PR #37 merged.
Close issue.

from pep8speaks.