question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

starter-workflow template gives `Resource not accessible by integration`

See original GitHub issue

Hi there,

I’ve implemented the exact Labeler workflow as the starter-workflow template in the dir path .github/workflows/label.yml.

I have also added the .github/labeler.yml file with the configuration below:

Trader: packages/trader/**/*

Bot: packages/bot/**/*

Core: packages/core/**/*

Components: packages/components/**/*

Shared: packages/shared/**/*

The action is recognised and runs on PR, however the Labeler action resolves with the following error:

##[error]HttpError: Resource not accessible by integration
##[error]Resource not accessible by integration
##[error]Node run failed with exit code 1

Googling seems to relate that error with invalid access to the repo by the action app, so I thought I’d create an issue and disable the action for now, but would be happy to know if there’s something I have missed out that will be able to solve this issue for me.

Thanks.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:45
  • Comments:80 (21 by maintainers)

github_iconTop GitHub Comments

20reactions
GregTheGreekcommented, Oct 3, 2019

What is the end solution?

16reactions
ylemkimoncommented, Aug 8, 2020

tl;dr, change

on:
- pull_request

to

on:
- pull_request_target

GitHub has introduced a new event type: pull_request_target, which allows to run workflows from base branch and pass a token with write permission.

In order to solve this, we’ve added a new pull_request_target event, which behaves in an almost identical way to the pull_request event with the same set of filters and payload. However, instead of running against the workflow and code from the merge commit, the event runs against the workflow and code from the base of the pull request. This means the workflow is running from a trusted source and is given access to a read/write token as well as secrets enabling the maintainer to safely comment on or label a pull request. This event can be used in combination with the private repository settings as well.

Read more comments on GitHub >

github_iconTop Results From Across the Web

"Resource not accessible by integration" on github post /repos ...
I explicitly assigned allowed all permissions in the workflow but it still doesn't work. Permissions for GH Token are also set to read/write....
Read more >
Debug "Resource not accessible by integration" error when ...
This error basically talks about a permission issue. When working with Github apps, you may not have set the necessary permission to access...
Read more >
Changing path based labels to use Github Actions - Development ...
An example of how it looks like: github.com/ekohl/community-templates ... Issue: starter-workflow template gives `Resource not accessible by integration`.
Read more >
Deploying to OpenShift using GitHub Actions
The OpenShift starter workflow uses the Red Hat GitHub Actions to help you get an application up and running by providing a workflow...
Read more >
Create a CI/CD pipeline for Amazon ECS with GitHub Actions ...
It also integrates with other core AWS services, such as Amazon ... to perform integration tests with components that are not reachable ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found