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.
expose defaults: run: working-directory: as env variable?
See original GitHub issueRecently the following was a welcome addition to the runner yaml syntax:
defaults:
run:
working-directory: scripts
Some repos are actually several projects/packages/gems, etc, and they may use this feature. Often, various config files would be located in the working-directory, and custom actions may be loading them.
Hence, exposing working-directory as an env variable would allow the custom actions to make use of it. At present, the setting only seems to be used by run/script actions…
NOTE: if the feature request has been agreed upon then the assignee will create an ADR. See docs/adrs/README.md
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I offered to do the work and submit a PR but never received confirmation from the github team if they were onboard.
Yes, and I did double check.
My feature request is that it be exposed (readonly) so custom actions can use it. As mentioned above, Ruby world could use It for reading config files. I suspect more apps may also have the same need. Granted, custom actions are not
run:, but it seemed like an odd distinction fordefaults:…