Resource not accessible by integration error

[Thomas-Boi]

This error is generated by the comment step in the Check SVGs workflow:

The interesting thing is this step works fine if the PR is opened by a branch inside the repo:

I will look more into this. This seems like another issue with access or auth.

[pan3793]

Encounter same issue on fork repo, do you find the solution?

[amacado]

@pan3793 currently @Thomas-Boi is working for finding a solution. This is more like a GitHub actions limitation and not a specific devicon problem.

There is f.e. this comment action https://github.com/mshick/add-pr-comment/ which solves this limitation by creating a proxy service for commenting on forked branches. But this requires to have a proxy up and running, which needs to be maintained.. Maybe we can find a simpler solution for this.

[Thomas-Boi]

So I poke around a bit more. It seems that the repo you mentioned was correct. No matter which Action I used, it got blocked whenever it's a fork. After doing some more research, the reason and solution can be found here. However, this requires a private repo, which obviously can't be done for us.

I have seen an interesting way to by pass this issue. @nyurik (see here create a cron job/schedule workflow that runs every 5 mins and checks whether there's a new PR. If there is, find the workflow associated, download the artifacts, do its thing, then post on the PR. This is actually the inspiration for my post

I'll keep digging and see what I can come up with. It seems like many people in the community have this complaint too and GitHub is looking into it. Further updates will probably go into the discussion since this is bigger than the check_svg workflow.

[pan3793]

Found a simple solution to solve this, see detail at housepower/ClickHouse-Native-JDBC#292

[Thomas-Boi]

Hi @pan3793 ,

I actually saw this resource when I was researching for a solution. At first, I was hesitant about this because of something that I found in the blog:

However, it seems like your code works and it's in a public repo so I wonder if there was an update. I can look into it more and see if it works cause this seems cleaner than the current way I'm doing it.

Thanks for the tip 😄

[pan3793]

I also hesitated until saw the next paragraph header Improvements for public repository forks 🤣

[Thomas-Boi]

Lol damn you are right 😆. Just scrolling down would have save me an entire evening working with the workflow_run thing. Thanks for the tip. I'll definitely implement this now

[nyurik]

I have seen an interesting way to by pass this issue. @nyurik (see here create a cron job/schedule workflow that runs every 5 mins and checks whether there's a new PR. If there is, find the workflow associated, download the artifacts, do its thing, then post on the PR. This is actually the inspiration for my post

There is now an official way to do this after I spoke with github about the issue. See https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#workflow_run -- much more efficient than using the scheduler, but otherwise it is pretty much the same concept as I originally proposed.

[Thomas-Boi]

Thanks nyurik! We ended up using the workflow_run just as you said. I'm also looking into the pull_request_target as well. Props for the cool work around that you thought of at first though.