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

The Publish Test Report step fails from forked repos #62

Closed
alvarosanchez opened this issue Nov 20, 2020 · 4 comments · Fixed by #76
Closed

The Publish Test Report step fails from forked repos #62

alvarosanchez opened this issue Nov 20, 2020 · 4 comments · Fixed by #76

Comments

@alvarosanchez
Copy link
Member

It is because we use secrets.GITHUB_TOKEN (which belongs to the actor triggering the action) instead of secrets.GH_TOKEN (which belongs to micronaut-build and has permissions).

https://github.com/micronaut-projects/micronaut-project-template/blob/master/.github/workflows/gradle.yml#L45

@alvarosanchez
Copy link
Member Author

This is the original issue report: ScaCap/action-surefire-report#31

@alvarosanchez
Copy link
Member Author

Using GH_TOKEN doesn't help. @pgressa tested it at 1843d06 (#212) an it failed with:

Error: You must authenticate via a GitHub App.

@alvarosanchez
Copy link
Member Author

Maybe we could switch to a different action: shyim/junit-report-annotations-action#3 (comment)

@alvarosanchez
Copy link
Member Author

The reason why Personal Access Tokens (GH_TOKEN) don't work is explained here: https://github.community/t/create-update-check-runs-via-github-api-using-a-personal-token/14690

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

Successfully merging a pull request may close this issue.

1 participant