update readme

Author: drewmullen

.github/workflows/comment.yml

@@ -0,0 +1,49 @@
+name: build
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  build:
+    if: >
+      startsWith(github.event.comment.body, 'build')
+      && startsWith(github.event.issue.pull_request.url, 'https://')
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: print comment body
+      run: echo ${{ github.event.comment.body }}
+  
+    - name: set body comments
+      run: |
+        set -eu
+        build_dir=$( cut -d ' ' -f 2 <<< '${{ github.event.comment.body }}' )
+        buckets=$( cut -d ' ' -f 3- <<< "${{ github.event.comment.body }}" )
+        echo $build_dir
+        echo $buckets
+
+    - name: 'Load PR Details'
+      id: load-pr
+      run: |
+        set -eu
+        resp=$(curl -sSf \
+          --url ${{ github.event.issue.pull_request.url }} \
+          --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
+          --header 'content-type: application/json')
+        echo $resp
+        sha=$(jq -r '.head.sha' <<< "$resp")
+        echo "::set-output name=head_sha::$sha"
+        # comments_url=$(jq -r '.comments_url' <<< "$resp")
+        # echo "::set-output name=comments_url::$comments_url"
+        # branch=$(jq -r '.branch' <<< "$resp")
+        # echo "::set-output name=comments_url::$comments_url"
+
+    # - uses: actions/checkout@v2
+    #   with:
+    #     ref: ${{ github.event.client_payload.ref }}
+
+    # - name: cat repo file
+    #   run: cat output.txt
+    #   working-directory: ${{ github.event.client_payload.project }}

README.md

@@ -1,10 +1,12 @@
 # Execute a github workflow manually
 
+Below are several examples for how to kick off workflow jobs manually via curl (or any external event)
+
 ## Create workflow at .github/workflows/file.yml
 
 Notice the `event_type` [matches](https://github.com/drewmullen/actions-playground/blob/fd3721ba3c8350995a77c570fbf3a0e0fb1c2724/.github/workflows/external_echo.yml#L5) the workflow field: `on.repository_dispatch.types`. the workflow file name does not need to match.
 
-## To Execute
+## Execute a basic job
 
 ```bash
 $ curl -XPOST -u "drewmullen" \
@@ -18,7 +20,7 @@ Enter host password for user 'drewmullen': <YOUR PAT>
 
 ## Specify a branch
 
-`repository_dispatch` always uses master branch. To use another branch, view [this workflow](https://github.com/drewmullen/actions-playground/blob/fd3721ba3c8350995a77c570fbf3a0e0fb1c2724/.github/workflows/repo_dispatch.yml) and set `client_payload.ref`:
+`repository_dispatch` always uses master branch. To use another branch, view [this workflow](https://github.com/drewmullen/actions-playground/blob/master/.github/workflows/repo_dispatch.yml) and set `client_payload.ref`:
 
 ```bash
 curl -XPOST -u "drewmullen" \
@@ -32,7 +34,7 @@ curl -XPOST -u "drewmullen" \
 
 ## Condition steps to run based on input
 
-If you'd like the same event to kick of specific jobs, use the `if` [condition](https://github.com/drewmullen/actions-playground/blob/fd3721ba3c8350995a77c570fbf3a0e0fb1c2724/.github/workflows/multi_repo_dispatch.yml).
+If you'd like the same event to kick of specific jobs, use the `if` [condition](https://github.com/drewmullen/actions-playground/blob/master/.github/workflows/multi_repo_dispatch.yml).
 
 ```bash
 curl -XPOST -u "drewmullen" \
@@ -44,6 +46,21 @@ curl -XPOST -u "drewmullen" \
 
 [Example CI Output](https://github.com/drewmullen/actions-playground/runs/536598658?check_suite_focus=true)
 
+
+## Multiple dirs, same step
+
+[multi_single_step.yml](https://github.com/drewmullen/actions-playground/blob/master/.github/workflows/multi_single_step.yml)
+
+[Example CI Output](https://github.com/drewmullen/actions-playground/runs/536824189?check_suite_focus=true)
+
+
+## Run from a container
+
+[container.yml](https://github.com/drewmullen/actions-playground/blob/master/.github/workflows/container.yml)
+
+[Example CI Output](https://github.com/drewmullen/actions-playground/runs/536598658?check_suite_focus=true)
+
+
 ## Create a PAT
 
 https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line