Resource not accessible by integration #630
Replies: 7 comments
-
Same here… |
Beta Was this translation helpful? Give feedback.
-
What does the |
Beta Was this translation helpful? Give feedback.
-
I'm seeing this issue as well after we migrated to GitHub Enterprise. 🤔 |
Beta Was this translation helpful? Give feedback.
-
The problem were missing workflow permissions. (needs to be read and write, obviously) It needs to be enabled on the enterprise level and can then only be more restrictive on organization and repository level. |
Beta Was this translation helpful? Give feedback.
-
@mrackwitz Thank you for investigating this issue. Am I correct in assuming that this means there is nothing I can do on my end, and that changing the settings for each repository will solve the problem? |
Beta Was this translation helpful? Give feedback.
-
Indeed! I think the only thing you could possibly do is add further documentation, but I hope already by just sharing my solution in this issue, others who run into it, will find it. Thanks for this amazing little tool, Katsumi. 🙏 |
Beta Was this translation helpful? Give feedback.
-
One more, if you use reusable workflows (e.g. via permissions:
# other permissions...
# This workflow needs write access to the checks to publish
# the results of the tests via xcresulttool.
checks: write |
Beta Was this translation helpful? Give feedback.
-
We have unit + UI tests running on wrapper using my SPM package.
Tests running solid and file is accessible when echo-ing it etc.
But for some reason when running this action on this specific repo - the results are inaccessible. (Both when tests passed or failed)
We are using this action on different repos, on some we are running on default directory and in some in sub-directories and everything works. I tried the same here - did not help.
Action's log:
Printing the report through bash commands:
Beta Was this translation helpful? Give feedback.
All reactions