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 specify location of Cargo.toml #30

Closed
BD103 opened this issue Aug 25, 2024 · 0 comments · Fixed by #33
Closed

Unable to specify location of Cargo.toml #30

BD103 opened this issue Aug 25, 2024 · 0 comments · Fixed by #33
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@BD103
Copy link
Collaborator

BD103 commented Aug 25, 2024

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant