Merge pull request #7 from replicatedhq/workingdir

Add workingDirectory option for publishing a subdirectory

README.md

@@ -57,6 +57,19 @@ jobs:
         environment: 'production'
 ```
 
+Optionally, you can also pass a `workingDirectory` key to the action. This will allow you to specify a subdirectory of the repo to run the Wrangler command from.
+
+```yaml
+jobs:
+  deploy:
+    # ... previous configuration ...
+    steps:
+      uses: cloudflare/wrangler-action@1.0.0
+      with:
+        # ... api key and email ...
+        workingDirectory: 'subfoldername'
+```
+
 ## Use cases
 
 ### Deploying when commits are merged to master

action.yml

@@ -15,3 +15,5 @@ inputs:
     required: true
   environment:
     description: "The environment you'd like to publish your Workers project to - must be defined in wrangler.toml"
+  workingDirectory:
+    description: "The relative path which Wrangler commands should be run from"

entrypoint.sh

@@ -30,10 +30,19 @@ export CF_API_KEY="$INPUT_APIKEY"
 
 npm i @cloudflare/wrangler -g
 
+if ! [ -z "$INPUT_WORKINGDIRECTORY" ]
+then
+  cd $INPUT_WORKINGDIRECTORY
+fi
+
 if [ -z "$INPUT_ENVIRONMENT" ]
 then
   wrangler publish
 else
   wrangler publish -e "$INPUT_ENVIRONMENT"
 fi
 
+if ! [ -z "$INPUT_WORKINGDIRECTORY" ]
+then
+  cd $HOME
+fi