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: HttpError: Resource not accessible by integration #30

Open
fgdrf opened this issue Oct 10, 2021 · 6 comments
Open

Error: HttpError: Resource not accessible by integration #30

fgdrf opened this issue Oct 10, 2021 · 6 comments

Comments

@fgdrf
Copy link

fgdrf commented Oct 10, 2021

I used spotbugs-githuib-action in udig-platform project worklow right after the maven build:

    - name: Run uDig product & sdk build (parallel)
      run: mvn install -B -Pproduct,sdk,test -DskipTests spotbugs:check --fail-at-end -T4
    - uses: jwgmeligmeyling/spotbugs-github-action@v1.2
      with:
        path: '**/spotbugsXml.xml'

spotbugsXml.xml are generated (checked locally) but I get http-errors. Proviously I testetd with version from master uses: jwgmeligmeyling/spotbugs-github-action@master but sometimes I got the same errors

see https://github.com/locationtech/udig-platform/pull/550/checks?check_run_id=3847205371#step:10:243

Any ideas whats going wrong?

@fgdrf
Copy link
Author

fgdrf commented Oct 10, 2021

btw on master with the same setup the build was fine, while it failed on pull request

@jwgmeligmeyling
Copy link
Owner

Was it an external pull request?

@fgdrf
Copy link
Author

fgdrf commented Oct 10, 2021 via email

@fgdrf
Copy link
Author

fgdrf commented Oct 11, 2021

@jwgmeligmeyling I can confirm that the build is fine if the branch to create the pull-request from is in the same repository (see locationtech/udig-platform#554)

Anything we can do to allow pulls from external repositories?

@jwgmeligmeyling
Copy link
Owner

Try pull_request_target instead of pull_request as workflow event target.

We're struggling with this limitation in this repository as well. See; #19 (comment)

@hypery2k
Copy link

You can also try to add this to your GH workflow:

permissions:
   ...
  checks: write # needed for spotbugs

See here

More details can be found here: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github\_token

You could also add the checks permission in your action directly.

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

No branches or pull requests

3 participants