Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

JUnit report annotation issue despite proper reporting #3

Closed
opatry opened this issue Dec 17, 2023 · 2 comments
Closed

JUnit report annotation issue despite proper reporting #3

opatry opened this issue Dec 17, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@opatry
Copy link
Owner

opatry commented Dec 17, 2023

Describe the bug
When running CI jobs, the test reports are published thanks to Mike Penz's action-junit-report Github action.

Each time it's executed, the following annotation is reported:

Caution

❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration)

Warning

⚠️ This usually indicates insufficient permissions. More details: mikepenz/action-junit-report#23

To Reproduce
Steps to reproduce the behavior:

  1. Any PR or main build running tests

Expected behavior
No annotation "❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration)" is expected

Screenshots
action-junit-report

@opatry opatry added the bug Something isn't working label Dec 17, 2023
@opatry
Copy link
Owner Author

opatry commented Mar 5, 2024

Need to add

permissions:
    contents: read
    checks: write
    id-token: write

Right after runs-on

@opatry opatry closed this as completed Aug 14, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
@opatry and others