You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #29 I created a standalone Cargo project within a subdirectory. Because it is not apart of any workspace and not in the root directory, cargo-cache fails to discover it. Here is the failed run that brought this to my attention.
While it is possible to specify the target directory, it is not possible to specify the Cargo.toml path. This can easily be fixed by passing --manifest-path to most Cargo commands.
Prepare all required actions
Getting action download info
Download action repository 'actions/cache@v4' (SHA:0c45773b623bea8c8e75f6c82b208c3cf94ea4f9)
Download action repository 'BD103/cargo-sweep@v1' (SHA:4f8057c958ff7f47b918db32aae950a4b41c46ba)
Run ./
Run if [ -f "Cargo.lock" ]; then
Cargo.lock file does not exist, creating it...
cargo 1.80.1 (376290515 2024-07-16)
error: could not find `Cargo.toml` in `/home/runner/work/cargo-cache/cargo-cache` or any parent directory
Error: Process completed with exit code 101.
The text was updated successfully, but these errors were encountered:
In #29 I created a standalone Cargo project within a subdirectory. Because it is not apart of any workspace and not in the root directory,
cargo-cache
fails to discover it. Here is the failed run that brought this to my attention.While it is possible to specify the
target
directory, it is not possible to specify theCargo.toml
path. This can easily be fixed by passing--manifest-path
to most Cargo commands.The text was updated successfully, but these errors were encountered: