It seems that Danger doesn't support fine-grained access tokens #1433

deiga · 2023-04-04T12:11:07Z

deiga
Apr 4, 2023

Does anyone know if that's true of if I'm just misconfiguring something?
Were seeing 403 - Resource not accessible by personal access token

Answered by orta

Apr 4, 2023

I don't see a reason why it wouldn't work, do you know what resources its failing on? You might need to turn on debug mode or use verbose

View full answer

orta · 2023-04-04T13:33:25Z

orta
Apr 4, 2023
Maintainer

I don't see a reason why it wouldn't work, do you know what resources its failing on? You might need to turn on debug mode or use verbose

4 replies

deiga Apr 5, 2023
Author

This is the error output we are seeing without debug or verbose:

bundler: failed to load command: danger (/Users/distiller/vendor/bundle/ruby/2.7.0/bin/danger)
Traceback (most recent call last):
    37: from /Users/distiller/.gem/ruby/2.7.6/bin/bundle:23:in `<main>'
    36: from /Users/distiller/.gem/ruby/2.7.6/bin/bundle:23:in `load'
    35: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/exe/bundle:36:in `<top (required)>'
    34: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
    33: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/exe/bundle:48:in `block in <top (required)>'
    32: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/cli.rb:25:in `start'
    31: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
    30: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/cli.rb:31:in `dispatch'
    29: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
    28: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
    27: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
    26: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/cli.rb:483:in `exec'
    25: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/cli/exec.rb:23:in `run'
    24: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/cli/exec.rb:58:in `kernel_load'
    23: from /Users/distiller/.gem/ruby/2.7.6/gems/bundler-2.3.15/lib/bundler/cli/exec.rb:58:in `load'
    22: from /Users/distiller/vendor/bundle/ruby/2.7.0/bin/danger:23:in `<top (required)>'
    21: from /Users/distiller/vendor/bundle/ruby/2.7.0/bin/danger:23:in `load'
    20: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/bin/danger:5:in `<top (required)>'
    19: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
    18: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/lib/danger/commands/runner.rb:73:in `run'
    17: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/lib/danger/danger_core/executor.rb:29:in `run'
    16: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/lib/danger/danger_core/dangerfile.rb:280:in `run'
    15: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/lib/danger/danger_core/environment_manager.rb:52:in `fill_environment_vars'
    14: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/lib/danger/request_sources/github/github.rb:122:in `fetch_details'
    13: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/danger-8.6.1/lib/danger/request_sources/github/github.rb:132:in `fetch_issue_details'
    12: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/octokit-4.25.1/lib/octokit/connection.rb:19:in `get'
    11: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/octokit-4.25.1/lib/octokit/connection.rb:156:in `request'
    10: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/sawyer-0.9.2/lib/sawyer/agent.rb:99:in `call'
     9: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.0/lib/faraday/connection.rb:200:in `get'
     8: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.0/lib/faraday/connection.rb:516:in `run_request'
     7: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.0/lib/faraday/rack_builder.rb:154:in `build_response'
     6: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-retry-1.0.3/lib/faraday/retry/middleware.rb:140:in `call'
     5: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/octokit-4.25.1/lib/octokit/middleware/follow_redirects.rb:61:in `call'
     4: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/octokit-4.25.1/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
     3: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.0/lib/faraday/middleware.rb:18:in `call'
     2: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.0/lib/faraday/response.rb:61:in `on_complete'
     1: from /Users/distiller/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.0/lib/faraday/middleware.rb:19:in `block in call'
/Users/distiller/vendor/bundle/ruby/2.7.0/gems/octokit-4.25.1/lib/octokit/response/raise_error.rb:14:in `on_complete': GET https://api.github.com/repos/amboss-mededu/ios-avocado-spring/issues/1102: 403 - Resource not accessible by personal access token // See: https://docs.github.com/rest/reference/issues#get-an-issue (Octokit::Forbidden)
Exited with code exit status 1

I guess it's just missing permissions for reading issues?

orta Apr 5, 2023
Maintainer

Yep, looks like it to me

deiga Apr 6, 2023
Author

Yup, that solved it. I think these are the permissions I needed to set. Maybe those could be updated in the docs?

dkniffin Jun 9, 2025

I ran into issues even with these settings. It turns out I needed my bot user to be in my organization. "Outside collaborator" (aka only permissions on one repo) wasn't enough. Once the bot was a member of my org, I saw an additional option under "Resource owner" when generating the token. Generating it that way worked.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

It seems that Danger doesn't support fine-grained access tokens #1433

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 4 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

It seems that Danger doesn't support fine-grained access tokens #1433

Uh oh!

deiga Apr 4, 2023

Replies: 1 comment · 4 replies

Uh oh!

orta Apr 4, 2023 Maintainer

Uh oh!

deiga Apr 5, 2023 Author

Uh oh!

orta Apr 5, 2023 Maintainer

Uh oh!

deiga Apr 6, 2023 Author

Uh oh!

dkniffin Jun 9, 2025

deiga
Apr 4, 2023

Replies: 1 comment 4 replies

orta
Apr 4, 2023
Maintainer

deiga Apr 5, 2023
Author

orta Apr 5, 2023
Maintainer

deiga Apr 6, 2023
Author