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.

Caught error trying to update branch: Resource not accessible by integration

See original GitHub issue

Hey. We were trying out the action in our project and it doesn’t update the branch in PR (which belongs to a forked project) whenever a commit gets pushed to the repository.

I see the following error in the Actions tab

Handling push event on ref 'refs/heads/master'
PR-425
  Evaluating pull request #425...
  PR_FILTER=all, checking if this PR's branch needs to be updated.
  All checks pass and PR branch is behind base branch.
  Updating branch 'testing' on pull request #425 with changes from ref 'master'.
  Attempting branch update...
  ##[error]Caught error trying to update branch: Resource not accessible by integration
  Branch update failed, will retry in 300ms, retry #0 of 5.
  Attempting branch update...
  ##[error]Caught error trying to update branch: Resource not accessible by integration
  Branch update failed, will retry in 300ms, retry #1 of 5.
  Attempting branch update...
  ##[error]Caught error trying to update branch: Resource not accessible by integration
  Branch update failed, will retry in 300ms, retry #2 of 5.
  Attempting branch update...
  ##[error]Caught error trying to update branch: Resource not accessible by integration
  Branch update failed, will retry in 300ms, retry #3 of 5.
  Attempting branch update...
  ##[error]Caught error trying to update branch: Resource not accessible by integration
  Branch update failed, will retry in 300ms, retry #4 of 5.
  Attempting branch update...
  ##[error]Caught error trying to update branch: Resource not accessible by integration
  ##[error]Resource not accessible by integration

We are using the default yml config as mentioned in the documentation

Is this a limitation of this Github Action? Any help is really appreciated. Thanks!