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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Resource not accessible by Integration #31

Open
Vishruth-S opened this issue Oct 21, 2020 · 4 comments · May be fixed by #296
Open

Error: Resource not accessible by Integration #31

Vishruth-S opened this issue Oct 21, 2020 · 4 comments · May be fixed by #296
Assignees

Comments

@Vishruth-S
Copy link

I added greetings to my repository, but I am getting the following error on pull requests submitted by new contributors.
Error: Resource not accessible by Integration

temp4

Here is my greetings.yml file

name: Greetings

on: [pull_request]

jobs:
  greeting:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/first-interaction@v1
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        issue-message: ''
        pr-message: "Hi there :wave: Congratulations on sending your first Pull request here :sparkles:\n I hope that you have followed the contribution guidlines"

I tried searching for a solution to fix this but couldn't find one. So I am not sure if this is caused by something from my end or if this is some kind of a bug...

@andymckay andymckay transferred this issue from actions/starter-workflows Nov 9, 2020
@obnoxxx
Copy link

obnoxxx commented Jan 19, 2021

same here.

@pllim
Copy link

pllim commented Feb 3, 2021

You need pull_request_target for it to work. See https://securitylab.github.com/research/github-actions-preventing-pwn-requests

@garg3133
Copy link

garg3133 commented Feb 5, 2021

Same thing is happening with me.

mestery added a commit to mestery/ipdk that referenced this issue Jul 14, 2022
Per [1], we need to use pull_request_target instead of pull_request
here. The tl;dr is that this runs as the *users* credentials, but they
may not have access to the repo.

See also [2].

[1] https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
[2] actions/first-interaction#31

Signed-off-by: Kyle Mestery <mestery@mestery.com>
mestery added a commit to mestery/ipdk that referenced this issue Jul 14, 2022
Per [1], we need to use pull_request_target instead of pull_request
here. The tl;dr is that this runs as the *users* credentials, but they
may not have access to the repo.

See also [2].

[1] https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
[2] actions/first-interaction#31

Signed-off-by: Kyle Mestery <mestery@mestery.com>
mestery added a commit to mestery/ipdk that referenced this issue Jul 14, 2022
here. The tl;dr is that this runs as the *users* credentials, but they
may not have access to the repo.

See also [2].

[1] https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
[2] actions/first-interaction#31

Signed-off-by: Kyle Mestery <mestery@mestery.com>
FanJups added a commit to osscameroon/js-generator that referenced this issue Oct 8, 2022
This PR #150 failed with this message:

Adding message: Thanks for opening your first pull request 😊 ! We really appreciate your work. Happy Coding 🎉🎊 ! to pull request 150
Error: Resource not accessible by integration

After investigating this first-interaction issue actions/first-interaction#31 , we decided to apply these changes.

This article from Github also looks good.
@ncalteen
Copy link
Collaborator

This should also be addressed in #296 :)

@ncalteen ncalteen self-assigned this Feb 22, 2024
@ncalteen ncalteen linked a pull request Feb 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@pllim @ncalteen @obnoxxx @garg3133 @Vishruth-S and others