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 same workflow for push and pull_request doesn't produce "Test Report" when run on pull_request #50

Open
skarakhanov opened this issue Feb 12, 2021 · 4 comments

Comments

@skarakhanov
Copy link

Hi!
I've got a workflow which worked just fine on push.
But when I tried to add a pull_request trigger, it didn't produce "Test Report" with error annotations.
To clarify more, in my configuration exactly the same workflow causes two builds to be run. One of these builds (on push) ends up with "Test Report" present but the other one (on pull_request) doesn't have "Test Report".
Project is Java, built with Gradle.

@mustaphazorgati
Copy link

mustaphazorgati commented Mar 18, 2021

Hey @jmisur,
I have the same issue on this workflow: https://github.com/Taskana/taskana/runs/2138524231?check_suite_focus=true
It works fine for master builds but it seems to now have permissions on pull requests.
Error: Resource not accessible by integration. Is there anything we can do about this?

@jmisur
Copy link
Contributor

jmisur commented Mar 23, 2021

I really don't have an idea what could be the problem. We're successfully using it for PRs and for master builds. Of course it doesn't work for forked repos but that's a different problem. Are you using default github token provided by workflow? https://docs.github.com/en/actions/reference/authentication-in-a-workflow

@mustaphazorgati
Copy link

Hey @jmisur,
thanks for the reply.

Of course it doesn't work for forked repos but that's a different problem.

We have the authentication issue because we work fork-based. I assume that @skarakhanov has the same issue. Is there anything we can do about it or do we have to wait until GitHub releases some changes regarding authentication on forks?

@skarakhanov
Copy link
Author

I have to add that for me this problem self-resolved at some point.
I just gave up trying to fix it and several days later we noticed that we do have test reports in our PRs.
Something might have happened on GitHub side.

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

No branches or pull requests

3 participants