anc95 / anc95/ChatGPT-CodeReview

Github Actions version doesn't seem to have enough permission to comment by default? Suggestions?

Open
#88 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
4.5k
Forks
461
PR merge metrics
No merged PRs in 30d

Description

I tried to switch from GitHub Apps version to GitHub Actions version, but it seems default GITHUB_TOKEN won't have enough permission to comment, not sure if using a PAT would be a good idea, anyone got the same issue and how do you deal with it? Thanks!

https://github.com/transmission-remote-gui/transgui/actions/runs/5038925037/jobs/9036731668?pr=1302

env:
    GITHUB_TOKEN: ***
    OPENAI_API_KEY: 
    MODEL: gpt-4
    top_p: 1
    temperature: 0.2
Error: Resource not accessible by integration
{
  name: 'event',
  id: '5038925037',
  err: {
    type: 'RequestError',
    message: 'Resource not accessible by integration',
    stack: 'HttpError: Resource not accessible by integration\n' +
      '    at /home/runner/work/_actions/anc95/ChatGPT-CodeReview/main/action/index.cjs:4070:21\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n' +
      '    at async Job.doExecute (/home/runner/work/_actions/anc95/ChatGPT-CodeReview/main/action/index.cjs:34389:18)',
    name: 'HttpError',
    status: 403,
    response: {
      url: 'https://api.github.com/repos/transmission-remote-gui/transgui/issues/1302/comments',

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked workflow run and the failure location in action/index.cjs, then review the shown token environment and GitHub comments endpoint. Done means the action's supported authentication and permission requirements are established and the reported comment request can be verified without the 403 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.