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

Unable to publish audit check from forked repos #28

Open
kaizencc opened this issue Oct 8, 2024 · 4 comments
Open

Unable to publish audit check from forked repos #28

kaizencc opened this issue Oct 8, 2024 · 4 comments

Comments

@kaizencc
Copy link

kaizencc commented Oct 8, 2024

I'm using rustsec/audit-check@v2 and receiving the following error:

No vulnerabilities were found
Warning: 1 warnings found!
Found 1 other
Error: Unable to publish audit check! Reason: HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run
Warning: It seems that this Action is executed from the forked repository.
Warning: GitHub Actions are not allowed to use Check API, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
Posting audit report here instead.


## Warnings

### Crate `futures-util` is yanked

No extra details provided.


No critical vulnerabilities were found, not marking check as failed

Or, the error will just be:

Warning: 1 warnings found!
Found 1 other
Error: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run

Some examples:
https://github.com/cdklabs/cdk-from-cfn/actions/runs/11216029024/job/31174437589
https://github.com/cdklabs/cdk-from-cfn/actions/runs/11242147829/job/31255195316

I'm not working on a forked repository but audit-check is forked. Is this a problem on my end or on yours?

@tarcieri
Copy link
Member

tarcieri commented Oct 8, 2024

I assume the problem here is this repo (i.e. on our end) is forked

@tarcieri
Copy link
Member

tarcieri commented Oct 8, 2024

The only way to fix it is to completely delete the repo and re-push the contents, which I can do, but ugh

@kaizencc
Copy link
Author

kaizencc commented Oct 9, 2024

any idea why this is happening now? from my perspective i just moved from targeting main branch to v2.0.0 tag.

@tarcieri
Copy link
Member

tarcieri commented Oct 9, 2024

I have no idea. I am the maintainer-of-last-resort for this repo and know very little about the internals of GitHub Actions

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

2 participants