Use workspace path from Github default env variables #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This project seems abandoned. I forked and fixed the action https://github.com/marketplace/actions/create-dotenv-file |
|
@baileytincher I took a look at some of your changes, they look pretty good! Sorry that I've been a bit absent from this repo - hopefully since I've resolved most of the items, I can now do releases a bit easier. If you're willing, it would be great to have a PR from you with your changes. If not, I'll just directly make a PR on my own, but it would be great to give you credit where it is due. Thanks for inspiring me to get back on my toes with this repo 😛 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This closes #7. The
GITHUB_WORKSPACEenvironment variable is provided to each Action, and should be used to know where the workspace is instead of hardcoding it.I still have to test this to look at any potential ramifications from how the workflow is currently working for other repos.