Merge pull request #3 from armhil/armhil-updating-readme

Update README.md

Author: armhil

README.md

@@ -1,5 +1,7 @@
 # Azure blobs - content uploader
 
+[![No real build - some simple tests & executing the action itself](https://github.com/armhil/azure-blobs-content-uploader/actions/workflows/main.yml/badge.svg)](https://github.com/armhil/azure-blobs-content-uploader/actions/workflows/main.yml)
+
 Azure Blobs Content Uploader is designed as a github action, to help developers upload their build artifacts to *multiple* az-storage accounts, taking into account the absolute paths / relative paths / recursive structure from your file system.
 
 It's especially meant to help with SPA developers (ex: artifacts of create-react-app) to quickly upload artifacts to a lot of storage accounts for redundancy and performance. 
@@ -8,6 +10,18 @@ It's especially meant to help with SPA developers (ex: artifacts of create-react
 
 To configure this job, you'll need a few things.
 
+### Your local files
+You should decide which directory to upload and to where on the storage accounts. This information is passed as parameters to the `*.yaml` file.
+See the `directoriesToUpload` parameter, which supports passing multiple directories. Note that while you can upload multiple directories, **they will be uploaded to the same location**.
+
+```yaml
+      - name: Upload Static Content
+        uses: armhil/azure-blobs-content-uploader@1.0.0
+        with:
+          azureBlobConfiguration: ${{ secrets.AZ_BLOB_CONFIGURATION }} # could be any secret that you have, see below for the format
+          directoriesToUpload: '[{"path": "test/integrationtest-directory", "shouldRecurse": "true" }]'
+```
+
 ### Azure blob details
 The content uploader supports uploading to multiple storage accounts, so you're going to need the *connection strings* of all the blob storages that you want to upload the files to.