-
Notifications
You must be signed in to change notification settings - Fork 22
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
Falende stickey-pull-request-comment integration #79
Comments
@floort. This is indeed the case but is does not block the PR. The PR is only blocked by no approving reviews yet. The reason the action fails is because of this github action that tries to deploy a version of a PR to the website for review:
This issue is described in the github action as a known problem.
We could solve it by not running the action for forked repos |
Good to hear that it's not a blocking issue. P.S. I noticed I'm switching between English and Dutch. Here the bug report template is English so I stuck to that without thinking about it. What's the preferred language for contributions? |
Zowel Nederlands als Engels is goed om een issue te melden. Het algoritmekader is in het Nederlands, daarom lijkt Nederlands logischer. Maar de bugs zijn in het Engels, waardoor dat ook een logische keuze is. Vervelend dat dit leidt tot een error. @berrydenhartog kan jij kijken of we deze functionaliteit uit kunnen zetten voor forked repo's? |
@ruthkoole. Ik zal de github action uitzetten voor forked repos |
Describe the bug
It appears that pull request from people without commit access to this repo get a the following error on a github action that blocks the pull request:
Run marocchino/sticky-pull-request-comment@331f8f5b4215f0445d3c07b4967662a32a2d3e31 Error: Resource not accessible by integration
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error
Screenshots
Additional context
Issue seems to be known by @berrydenhartog in a comment that is now removed from #72. Posting it here as a bug report as it's undocumented now.
The text was updated successfully, but these errors were encountered: