Skip to content

Commit dd854be

Browse files
committed
Run Prettier
1 parent f629f99 commit dd854be

1 file changed

Lines changed: 20 additions & 9 deletions

File tree

README.md

Lines changed: 20 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -331,11 +331,14 @@ change this behavior by setting `fail-on-proxy-error: true`.
331331
### "Resource not accessible by integration"
332332

333333
**Error message:**
334+
334335
```
335336
Error: Resource not accessible by integration
336337
```
337338
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.
339342
340343
**Solution 1:** Ensure you have the minimal required permissions:
341344
@@ -345,36 +348,44 @@ permissions:
345348
id-token: write
346349
```
347350

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:
349353

350354
```yaml
351355
permissions:
352-
contents: read # Repository metadata access
356+
contents: read # Repository metadata access
353357
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
356360
```
357361
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.
359367
360368
### "Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable"
361369
362370
**Error message:**
371+
363372
```
364373
Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
365374
```
366375
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.
368378

369379
**Solution:** Add the `id-token: write` permission to your workflow:
370380

371381
```yaml
372382
permissions:
373383
pull-requests: write
374-
id-token: write # Required for OIDC authentication
384+
id-token: write # Required for OIDC authentication
375385
```
376386

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.
378389

379390
### "No comment appears after reviews"
380391

0 commit comments

Comments
 (0)