-
-
Notifications
You must be signed in to change notification settings - Fork 39
Add PROJECT_PATH environment variable #116
Comments
Same issue here - we use a cargo workspace. |
Same -- see also actions-rs/cargo#59 |
Same, this would be useful |
Related to actions-rs/cargo#86 The best would be if it takes into account the current working directory:
See https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#defaultsrun |
We need this for our monorepo. See also #194 Ideally, I would suggest letting cargo do the work; it already has a In fact, other actions in the
|
I also hit this particular wall while integrating with my project. Posting to subscribe on further results! |
any updates? |
I need this as well. This issue seems to have become stale, but it is quite important. Not every repository has the Rust code / |
Do the checklist before filing an issue:
actions-rs
Actions?If you think it's a problem related to Github Actions in general, use GitHub Community forum instead: https://github.saobby.my.eu.orgmunity
Motivation
For a variety of reasons, many projects don't contain their
Cargo.toml
file in their root directory, or they have multiple sub-projects each with their ownCargo.toml
s. Would it be possible to make the project path configurable? That way the community would benefit from being able to run from a specified path.We've added this action to a few of our projects and I'm in the process of expanding that to others as it works well, but I've hit this issue which seems to block me from using it in projects such as here
and only the root directory `Cargo.toml in this repo hereEDIT: was mistaken about this particular linked repo being an example.Workflow example
Additional context
As far as I'm aware there's no way around this at the moment. Been looking for workarounds to this issue I'm facing and found the
working-directory
option here but turns out it can only be used withrun
and not withuses
.Found a PR here which seems to have resolved this in another action, hoping something similar would work with audit-check.
The text was updated successfully, but these errors were encountered: