CI workflow and .gitignore
file
#8
Annotations
4 errors and 13 warnings
cargo-clippy (ubuntu-22.04)
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
|
cargo-clippy (macos-12)
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
|
cargo-clippy (windows-2022)
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
|
cargo-test (windows-2022)
The process 'C:\Users\runneradmin\.cargo\bin\cargo.exe' failed with exit code 101
|
cargo-fmt
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@ae10961054e4aa8b4aa7dffede299aaf087aa33b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-clippy (ubuntu-22.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@b5b5f21f4797c02da247df37026fcd0a5024aa4d. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-clippy (ubuntu-22.04)
It seems that this Action is executed from the forked repository.
|
cargo-clippy (ubuntu-22.04)
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.
|
cargo-test (ubuntu-22.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@ae10961054e4aa8b4aa7dffede299aaf087aa33b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-clippy (macos-12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@b5b5f21f4797c02da247df37026fcd0a5024aa4d. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-clippy (macos-12)
It seems that this Action is executed from the forked repository.
|
cargo-clippy (macos-12)
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.
|
cargo-clippy (windows-2022)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@b5b5f21f4797c02da247df37026fcd0a5024aa4d. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-clippy (windows-2022)
It seems that this Action is executed from the forked repository.
|
cargo-clippy (windows-2022)
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.
|
cargo-test (macos-12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@ae10961054e4aa8b4aa7dffede299aaf087aa33b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-test (windows-2022)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@ae10961054e4aa8b4aa7dffede299aaf087aa33b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|