-
Notifications
You must be signed in to change notification settings - Fork 90
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
Add possibility to use custom workspace #30
Conversation
Hi! Yes, hopefully this could solve it |
I have re-based this and slightly altered what was here @tatsta & @helen I'd appreciate 👀 or responses if you find time. For me not having this is preventing me from having a release github action. I Could totally roll my own, but if #16 and this are anything to go by, the issue affects a lot of people. Differences:
Thanks to both. |
@iamdharmesh bumping back up for your review. |
Description of the Change
Add a possibility to specify workspace folder as environment variable
WORKSPACE_DIR
in case the Wordpress artefact files are located in custom folder. If environment variableWORKSPACE_DIR
is not setGITHUB_WORKSPACE
variable (and path) will be usedAlternate Designs
Tried to redefine
GITHUB_WORKSPACE
variable when passing it into the action, but that didn't work for me.Benefits
The actions is more reusable in other use cases
Possible Drawbacks
Verification Process
I tested on a fork with .distignore and .gitattributes, both seemed to work fine.
Checklist:
Applicable Issues
Changelog Entry