Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug: No fallback behavior for action runs on forks #44

Open
JoshuaKGoldberg opened this issue Dec 22, 2023 · 0 comments
Open

馃悰 Bug: No fallback behavior for action runs on forks #44

JoshuaKGoldberg opened this issue Dec 22, 2023 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@JoshuaKGoldberg
Copy link
Contributor

When this action runs on a fork and doesn't have permissions to fetch comments (am I using the right terminology?), we see the dreaded Resource not accessible by integration error. Example from JoshuaKGoldberg/create-typescript-app#1110 -> https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/7297169422/job/19886082551?pr=1110:

Run github/accessibility-alt-text-bot@v1.4.0
Run source /home/runner/work/_actions/github/accessibility-alt-text-bot/v1.4.0/queries.sh
Detected bad alt text: true
Event type: pr_description
GraphQL: Resource not accessible by integration (addComment)
Error: Process completed with exit code 1.

This is a similar issue to mtfoley/pr-compliance-action#368 -> mtfoley/pr-compliance-action#374.

Suggestion: can the bot log an informative message in the error about what it would post if it could? That way, if it's not able to actually post a comment, a useful error can still be logged.

@kendallgassner kendallgassner added the help wanted Extra attention is needed label Jan 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants