Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error 404 on Heroku Instance when posting comments.

See original GitHub issue

I tried a heroku instance, the github account invite went OK! successfully, but having issues posting comments and getting a 500 error. I have already and only updated the form action to my heroku url.

github account access token set to admin:repo_hook checked all under it.
copy and pasted a generated key.pem file to key RSA_PRIVATE_KEY Heroku settings -> config vars (web/dashboard)

@VincentTam I’m using your repo with the deploy branch. Any ideas?

Issue Analytics

State:
Created 4 years ago
Comments:16 (6 by maintainers)

Top GitHub Comments

2reactions

wini3dcommented, Sep 12, 2019

Finally I got it working! =) Somehow, I had to give full access token (checked all) which I know is not recommended. I only checked repo:invite and admin:repo_hook before based on a tutorial post I read earlier.

Edit: found an updated one that needs to set full repo access only

Thanks again for all the help @VincentTam 👍

0reactions

wini3dcommented, Sep 12, 2019

As the name suggests, public_repo can’t grant you rights to push PRs to private repos. It’s up to you to decide if your bot accepts invitations to private repos.

Yes, I am currently on a free plan so I have set it to public only. Thanks.

I’m not sure if admin:repo_hook is relevant since I dunno node.js and I got Staticman’s webhook working on GitHub with the legacy authentication method and v3 API without #288 and this scope.

I see, will try without this soon.