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.

Should this work on PRs raised from forks?

See original GitHub issue

I tried to use this instead of the default GHA, because token takes the PAT token. So that I can run an action on a PR from fork, but I get the following message:

[@octokit/rest] `const Octokit = require("@octokit/rest")` is deprecated. Use `const { Octokit } = require("@octokit/rest")` instead
[@octokit/rest] `const Octokit = require("@octokit/rest")` is deprecated. Use `const { Octokit } = require("@octokit/rest")` instead
##[error]Bad credentials

Is this expected behaviour or should it work?

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

andrzejnovakcommented, Aug 4, 2020

@peter-evans Indeed. I’ve complained successfully 😄 https://github.community/t/inconsistent-on-issue-behaviour/117189/16

1reaction

peter-evanscommented, Aug 4, 2020

A couple of new updates have been announced that could help here.

If your repository is private, you can now enable workflows from forks.
If your repository is public, there is a new pull_request_target event that is not subject to any token restrictions. I recommend using this event to comment on pull requests.