Does it work for PRs from forks?

Question

Does it work for PRs from forks?

Closed this issue 3 years ago · 8 comments

JAremko commented 5 years ago

I tried running it in my fork and it worked but it doesn't seem to work for PRs from forks.

Example and This is how error looks like

Answer 1 · 2019-12-15T07:41:14.000Z

Not sure about forks... I'll have a look, thanks for giving me an example

Answer 2 · 2019-12-20T20:41:16.000Z

Confirmed. It's an issue. I think it's because when you merge a fork the PR is in the repository you forked from. I'll have a look if this is possible with the Github actions token.

Answer 3 · 2019-12-20T20:54:12.000Z

@peter-grainger You probably can run cron jobs + use https://developer.github.com/v3/pulls/#list-pull-requests-files as a workaround. But it's kinda meh since the reaction to PR will be delayed 🤔

Answer 4 · 2019-12-21T07:29:26.000Z

@JAremko I think this is the same problem https://github.community/t5/GitHub-Actions/GitHub-Action-workflow-is-executed-for-a-PR-from-a-forked-repo/m-p/29579

I see why they would do this. You don't want people forking your repo to have full write access to your issues. Not sure there is a way around it :(

Answer 5 · 2019-12-21T17:39:56.000Z

Yeah not with actions. 🤔

Answer 6 · 2019-12-22T21:10:56.000Z

For anyone looking at this later other actions have the same problem with forks. Maybe at some point they will sort out the permissions. Here is a discussion on the labeller action actions/labeler#12

Answer 7 · 2020-12-17T22:53:57.000Z

Still open, was this ever resolved?

Answer 8 · 2022-01-03T20:27:53.000Z

Yes. You can now configure this!