-
-
Notifications
You must be signed in to change notification settings - Fork 39
Specify directory to run audit on #194
Comments
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 |
It seems this issue is a duplicate of #116 |
any updates? |
I'm also interested in this, since we're using a mono repository. This is a general problem with GitHub actions, because the
|
I'm also interested in this but have found a temporary solution. Just replace {CARGO_SUBDIR} with your cargo project directory in your repo and {DIRS_TO_REMOVE} with all the non-cargo directories in the top-level of your repo: jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
# Moves all files in sub dir to top-level dir
- run: cd $GITHUB_WORKSPACE && mv {CARGO_SUBDIR}/* .
# Delete directories not to be audited
- run: cd $GITHUB_WORKSPACE && rm -rf {DIRS_TO_REMOVE}
- uses: actions-rs/audit-check@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
|
+1 the workaround works, but is cumbersome... |
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.community
Motivation
My rust/cargo project isn't at the top level of my repo, so my audit check always fails because it can't find my Cargo.toml/Cargo.lock file and it doesn't take a
manifest-path
like other cargo commands do.Describe your idea, motivation, and how Rust community could benefit from this feature.
Workflow example
It would be awesome if the action would read
working-directory
or take amanifest-path
argAdditional context
I've tried a couple work arounds but couldn't get any of them working, I hope this isn't an invasive/difficult addition.
The text was updated successfully, but these errors were encountered: