Closed lukaswoellhaf closed 3 weeks ago
I have never tried this action on GHES but I would assume that it should just work if other actions also just work out of the box. The only known issue at this point is, that pull requests from forks are not supported in general but this would be unrelated to GHES.
To debug authentication issues you can check which permissions the used GitHub token actually has by expanding the "Set up job" step and then click on GITHUB_TOKEN Permissions:
According to the API documentation, the token needs "Actions" repository permissions (read)
.
Hey @lukaswoellhaf , were you able to solve your issue?
Hey @fgrosse sorry, totally forgot this issue was still open. Unfortunately I could not solve the issue. I have all the permissions on the GITHUB_TOKEN
provided in the screenshot, including the repository-projects
read access which should be enabled by default: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token.
I decided for another solution in the meantime. I will close this issue for now.
Hello first of thank you for this implementation - looks very promising :)
I'm currently trying to integrate the go-coverage-report inside a GHES pipeline. When trying to execute the go-coverage-report action step I get following error while fetching the artifact:
Im successfully checking out the repo and provide the necessary permission for the job, but it still seems to fail in
scripts/github-action.sh
:Question: Is this Github Action compatible with GHES out of the box or do I need to provide another Github base url to the action, to sucessfully authenticate?
Here is my complete GitHub action: