-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Allow specifying custom profiles #44
Conversation
617225e
to
d2ef737
Compare
Allow for users to specify a specific profile.
d2ef737
to
609508c
Compare
Thanks for the PR! The upload-rust-binary-action/main.sh Line 244 in 609508c
upload-rust-binary-action/main.sh Lines 251 to 252 in 609508c
upload-rust-binary-action/main.sh Line 263 in 609508c
See this code in cargo-llvm-cov for the directory name used. |
The `release` profile was hardcoded and will fail if we change the profile.
Good catch, thanks |
Set the default profile env var to "release" if it's not supplied.
Address feedback about handling special Cargo profiles.
Use the profile name provided by the user, always. We separate out a new variable for the profile directory name for clarity, and so we use the correct profile as requested by the user.
We were not supposed to change the name of the field we're pulling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Published in 1.14.0. |
Allow for users to specify a specific profile. I have a ci-specific profile, so it would be useful to be able to set a different profile in the action config.