Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration

Command failed: cargo metadata --all-features --format-version 1

error: could not find `Cargo.toml` in `/Users/runner/work/LibCST/LibCST` or any parent directory

Error: ENOENT: no such file or directory, opendir '/Users/runner/work/LibCST/LibCST/target'

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Unexpected input(s) 'working-directory', valid inputs are ['prefix-key', 'shared-key', 'key', 'env-vars', 'workspaces', 'cache-directories', 'cache-targets', 'cache-on-failure', 'cache-all-crates', 'save-if']

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

It seems that this Action is executed from the forked repository.

GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.

binary comparison to literal `Option::None`

the following explicit lifetimes could be elided: 'a

the following explicit lifetimes could be elided: 'a

deref which would be done by auto-deref

deref which would be done by auto-deref

deref which would be done by auto-deref

deref which would be done by auto-deref

deref which would be done by auto-deref