After update, Error 403: Resource not accessible by integration

[MarkEnverus]

This issue was closed but it persists
https://github.com/ncipollo/release-action/issues/129
I'm facing the same issue w/ github.com - i can't even use a personal token - if i do that I get the error "Error: Error undefined: Parameter token or opts.auth is required"

[ncipollo]

I don't think this is an issue in the action, it sounds like you might have an issue with your repo (was it forked?) or your workflow file is formatted incorrectly.

Checkout this issue which sounds similar: actions/toolkit#465. The issue they had was that it was a forked repo and secrets aren't available in those repos.

[DNA-PC]

I'm a bit confused by this.

I'm using a fork, that is a fork repo from another of my repositories.
The only secret I can think of is {{secrets.GITHUB_TOKEN}}, but I thought each repo would have its own, why would it try to use the one from the source repo?

[dadair-aptiv]

Think the solution is this: https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs. I had this same issue thinking it was the docker container. I needed to set the contents: write access.

I haven't tracked down why this repo in the organization needed this set for its workflows. The other repos didn't need it.

name: ...

on:
  ...
permissions:
  contents: write

jobs:
  ...

EDIT: Adding a mention to the original issue since it didn't link correctly #129

[DNA-PC]

Why would there need to be a "write" permission? What's being written? I thought my workflow failed because it was trying to read the GITHUB_TOKEN from its source repository.

[dadair-aptiv]

From my understanding, it needs the write permission to create a release. So you have to write the release to the repo. Not 100% sure if that is it though. Just what I am inferring on the testing i did. The documentation isn't there / clear.

[Vadorequest]

Thanks for bringing some context. I've tested and it works using your solution.

[scottw-kr]

Confirming this works on a fork.

Think the solution is this: https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs. I had this same issue thinking it was the docker container. I needed to set the contents: write access.

I haven't tracked down why this repo in the organization needed this set for its workflows. The other repos didn't need it.

name: ...

on:
  ...

permissions:
  contents: write

jobs:
  ...

[ncipollo]

You might want to double check the action settings in your repository. It's possible you don't have write access by default (Settings --> Action --> General --> Workflow permissions)

[dadair-aptiv]

That was set to Read and write permissions for me yet still couldn't do it. That was what I checked based on the other issue.

[ortegamarcel]

You might want to double check the action settings in your repository. It's possible you don't have write access by default (Settings --> Action --> General --> Workflow permissions)

@ncipollo Thanks, that solved my problem.

[gauntface]

I've noticed that I run into this issue in a forked repo only when I define a commit value.

Creating a release without a commit and the release and tags are created fine, with the commit and it fails.

[baydim]

GREAT INFO BROO