Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support "working-directory" input

See original GitHub issue

The action currently assumes there is exactly one Rust project and it’s located in the root of the repo. It would be great to support working-directory such as the one you can use with regular run in a workflow step.

Issue Analytics

State:
Created 4 years ago
Reactions:12
Comments:7 (2 by maintainers)

Top GitHub Comments

5reactions

dmontagucommented, Aug 26, 2020

Using the --manifest-path option to specify the Cargo.toml file seems to ensure the action works, but it doesn’t seem to get the paths right (they are relative to where Cargo.toml lives, not the repository root), so the feedback can’t be viewed from the files view of the PR. (Though they it does appear in the checks list.)

Any suggestions for a workaround?

0reactions

qwandorcommented, Apr 30, 2021

The problem with the --manifest-path approach is that it doesn’t use the .cargo/config under the crate directory. This may be a problem if it specifies a different build.target than the default, e.g. for embedded software that only builds on a particular architecture.