You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-9Lines changed: 20 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -331,11 +331,14 @@ change this behavior by setting `fail-on-proxy-error: true`.
331
331
### "Resource not accessible by integration"
332
332
333
333
**Error message:**
334
+
334
335
```
335
336
Error: Resource not accessible by integration
336
337
```
337
338
338
-
**Cause:** Insufficient GitHub token permissions for accessing PR data or creating comments. This typically occurs when the workflow lacks proper permissions for the repository.
339
+
**Cause:** Insufficient GitHub token permissions for accessing PR data or
340
+
creating comments. This typically occurs when the workflow lacks proper
341
+
permissions for the repository.
339
342
340
343
**Solution 1:** Ensure you have the minimal required permissions:
341
344
@@ -345,36 +348,44 @@ permissions:
345
348
id-token: write
346
349
```
347
350
348
-
**Solution 2:** If the minimal permissions don't work due to repository settings, try this expanded configuration:
351
+
**Solution 2:** If the minimal permissions don't work due to repository
352
+
settings, try this expanded configuration:
349
353
350
354
```yaml
351
355
permissions:
352
-
contents: read # Repository metadata access
356
+
contents: read # Repository metadata access
353
357
pull-requests: write # PR review and comment access
354
-
issues: read # Additional PR comment read access
355
-
id-token: write # OIDC authentication
358
+
issues: read # Additional PR comment read access
359
+
id-token: write # OIDC authentication
356
360
```
357
361
358
-
**Note:** Repository settings can vary, and some organizations may require additional permissions depending on their security policies. For organization-owned repositories, check that "Allow GitHub Actions to create and approve pull requests" is enabled in Settings → Actions → General → Workflow permissions.
362
+
**Note:** Repository settings can vary, and some organizations may require
363
+
additional permissions depending on their security policies. For
364
+
organization-owned repositories, check that "Allow GitHub Actions to create and
365
+
approve pull requests" is enabled in Settings → Actions → General → Workflow
366
+
permissions.
359
367
360
368
### "Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable"
361
369
362
370
**Error message:**
371
+
363
372
```
364
373
Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
365
374
```
366
375
367
-
**Cause:** Missing `id-token: write` permission. GitHub Actions only provides the OIDC token environment variables when this permission is explicitly granted.
376
+
**Cause:** Missing `id-token: write` permission. GitHub Actions only provides
377
+
the OIDC token environment variables when this permission is explicitly granted.
368
378
369
379
**Solution:** Add the `id-token: write` permission to your workflow:
370
380
371
381
```yaml
372
382
permissions:
373
383
pull-requests: write
374
-
id-token: write # Required for OIDC authentication
384
+
id-token: write # Required for OIDC authentication
375
385
```
376
386
377
-
Without `id-token: write`, the action cannot authenticate with the SkillLens backend and will fail immediately after fetching review data.
387
+
Without `id-token: write`, the action cannot authenticate with the SkillLens
388
+
backend and will fail immediately after fetching review data.
0 commit comments