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
[BUG] Request failed [403]: https://api.github.com/user #1368
Labels
Comments
Pretty sure someone tried to fix this recently and had to be reverted, open to carefully thought out PRs for it |
Is there a way to just suppress the error message instead of changing where it's run at? |
Probably, I think you'd need to look into how the API is called, as I assume it uses octokit for those API calls which would I think is writing the logs there. Could probably special case that specific API call somehow? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Danger sends errors to the output for failed https://api.github.com/user connections.
While this does not cause danger to error, it does cause anyone who looks at the output to think danger failed because of a permissions issue, and ignores everything else.
We use the auto created token in GitHub workflows for Danger as it provides the access we need and doesn't have too much access.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
How can we make this more clear that this is NOT causing any issues. Not sure if it shouldn't show, or someway to display differently that doesn't make the user feel danger failed due to the 403 error.
Screenshots
If applicable, add screenshots to help explain your problem.
Your Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: