-
-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Use RUNNER_TEMP environment variable instead of a hardcoded path #138
Conversation
Codecov Report
@@ Coverage Diff @@
## master #138 +/- ##
=======================================
Coverage 73.01% 73.01%
=======================================
Files 16 16
Lines 378 378
Branches 72 72
=======================================
Hits 276 276
Misses 92 92
Partials 10 10
|
Hi @xanantis and thank you for your PR. I'm still trying to understand what you're trying to achieve and what exactly the use case is for this and how that use case would work. Could you perhaps elaborate a bit more on that? Could you also tell us why you chose for an environment variable over an input variable and why you chose Currently it looks like the default value is never set, which will likely break current behaviour. What are your thoughts on this? |
@webbertakken Variable is set by a runner. It leads to the temporary directory of the current runner. And it is always defined. |
@xanantis Would you mind linking the source for this? |
@webbertakken Here is some info: runner-context. And this is the result of:
|
Because self-hosted runners can be placed anywhere, it is better to use an environment variable instead of a hardcoded path.