You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -71,10 +72,10 @@ Afterward, the `components` and `target` specified via inputs are installed in a
71
72
By default, this action sets the `RUSTFLAGS` environment variable to `-D warnings`.
72
73
However, rustflags sources are mutually exclusive, so setting this environment variable omits any configuration through `target.*.rustflags` or `build.rustflags`.
73
74
74
-
* If `RUSTFLAGS` is already set, no modifications of the variable are made and the original value remains.
75
-
* If `RUSTFLAGS` is unset and the `rustflags` input is empty (i.e., the empty string), then it will remain unset.
76
-
Use this, if you want to prevent the value from being set because you make use of `target.*.rustflags` or `build.rustflags`.
77
-
* Otherwise, the environment variable `RUSTFLAGS` is set to the content of `rustflags`.
75
+
-If `RUSTFLAGS` is already set, no modifications of the variable are made and the original value remains.
76
+
-If `RUSTFLAGS` is unset and the `rustflags` input is empty (i.e., the empty string), then it will remain unset.
77
+
Use this, if you want to prevent the value from being set because you make use of `target.*.rustflags` or `build.rustflags`.
78
+
-Otherwise, the environment variable `RUSTFLAGS` is set to the content of `rustflags`.
78
79
79
80
To prevent this from happening, set the `rustflags` input to an empty string, which will
80
81
prevent the action from setting `RUSTFLAGS` at all, keeping any existing preferences.
@@ -95,10 +96,10 @@ You can read more rustflags, and their load order, in the [Cargo reference].
95
96
The action works best on the GitHub-hosted runners, but can work on self-hosted ones too, provided the necessary dependencies are available.
96
97
PRs to add support for more environments are welcome.
0 commit comments