Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[v2.3.1] Resource not accessible by integration #181

Closed
yusancky opened this issue Jan 14, 2023 · 6 comments · Fixed by #222
Closed

[v2.3.1] Resource not accessible by integration #181

yusancky opened this issue Jan 14, 2023 · 6 comments · Fixed by #222

Comments

@yusancky
Copy link

yusancky commented Jan 14, 2023

First of all, thank you very much for developing such a useful and convenient Actions.

I was using v2.3.0 and it worked very well and helped me simplify some of my work. But just now, @dependabot opened a new pull request yusancky/AllUp-Satwiki#9 in my repository, which wants to upgrade this Actions to v2.3.1. However, the pull request did not pass the test and no comment was given - it failed in The comment gives an error.

Bump thollander/actions-comment-pull-request from 2.3.0 to 2.3.1 #43

Error: Resource not accessible by integration

Here's part of the workflow file. This workflow runs on Ubuntu-latest.

      - name: Preview on Pull Request
        if: ${{ github.event_name == 'pull_request' }}
        uses: thollander/actions-comment-pull-request@v2.3.1
        with:
          message: |
            # 预览
            ```go
            ${{ steps.fetch_make.outputs.ALLUP_CONTENT }}
            ```
            > **Note**
            > 上方的 wikitext 代码块因展示高亮便利而使用 Go 语言高亮器,敬请理解。
          reactions: eyes
          comment_tag: actions-wikitext-preview
@pigoz
Copy link

pigoz commented Jan 29, 2023

@yusancky how di you solve this? I have the same issue.

@yusancky
Copy link
Author

@yusancky how di you solve this? I have the same issue.

@pigoz Just use permissions.

permissions: 
   pull-requests: write 

Setting permissions for job also works.

@pigoz
Copy link

pigoz commented Jan 29, 2023

@yusancky how di you solve this? I have the same issue.

@pigoz Just use permissions.

permissions: 
   pull-requests: write 

Setting permissions for job also works.

Thank you!

@coolusaHD
Copy link

Please add this to the examples !!!

chukarave added a commit to wmde/new-lexeme-special-page that referenced this issue Jul 10, 2023
This occured due to changes in the package
thollander/actions-comment-pull-request starting v2.3.1
see thollander/actions-comment-pull-request#181
chukarave added a commit to wmde/new-lexeme-special-page that referenced this issue Jul 10, 2023
This occured due to changes in the package
thollander/actions-comment-pull-request starting v2.3.1
see thollander/actions-comment-pull-request#181
@dpo
Copy link

dpo commented Oct 29, 2023

That did not work for me, despite the documentation. GitHub said the yaml was invalid. Only permissions: write-all at the top level of the workflow worked.

@rodsotdia
Copy link

If someone is getting an error like Repository **** not found, it is likely that you are also using another kind of action in the job, like actions/checkout@v4, so you need set up more permissions like so:

permissions:
  pull-requests: write
  contents: read

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants