-
-
Notifications
You must be signed in to change notification settings - Fork 20
Support specifying the working directory as a parameter #113
Copy link
Copy link
Open
Labels
A-actionArea: the action itselfArea: the action itselfA-docsArea: documentation for the command and lintsArea: documentation for the command and lintsC-enhancementCategory: raise the bar on expectationsCategory: raise the bar on expectationsE-help-wantedCall for participation: Help is requested to fix this issue.Call for participation: Help is requested to fix this issue.
Description
Metadata
Metadata
Assignees
Labels
A-actionArea: the action itselfArea: the action itselfA-docsArea: documentation for the command and lintsArea: documentation for the command and lintsC-enhancementCategory: raise the bar on expectationsCategory: raise the bar on expectationsE-help-wantedCall for participation: Help is requested to fix this issue.Call for participation: Help is requested to fix this issue.
The choice of working directory matters for cargo config. Cargo will start looking for config info in the working directory and walk up from there. Regardless of what
--manifest-pathis passed to it, cargo cares about the working directory's build configuration.We need to be able to set a
working-directoryparameter, in case users have cargo config at the package level of a workspace. Otherwise, the action will run in the default location (likely, the workspace) and won't pick up the relevant config.We should use the test cases in this project to test: https://github.com/obi1kenobi/c-s-c-testcase-cargo-config-toml