feat(integration): add example how to decode buildingBlockRun inputs in GitHub action job step using jq

Author: grubmeshi

docs/integrations/github/github-actions.md

@@ -145,7 +145,36 @@ on:
         required: true
 ```
 
-This setup allows application teams to quickly and efficiently access automation workflows from the marketplace, enhancing their productivity and reducing the need for Git expertise.
+Within a job, you need to decode the `buildingBlockRun` input.
+Define a job step to decode all Building Block inputs as follows and provide them to following steps:
+```yaml
+jobs:
+  some-job:
+    runs-on: ubuntu-latest # ships with jq already!
+    steps:
+      # ... some other steps
+      - name: Decode buildingBlockRun inputs
+        id: decodeBuildingBlockInputs
+        shell: bash
+        env:
+          # pass in indirectly as env variable to avoid cluttering the job log with a large base64 string
+          BUILDING_BLOCK_RUN_INPUT: ${{ inputs.buildingBlockRun }}
+        run: |
+          set -euo pipefail
+          base64 -d <<<"$BUILDING_BLOCK_RUN_INPUT" \
+          | jq -er '
+            .spec.buildingBlock.spec.inputs
+            | unique_by(.key)
+            | .[]
+            | "\(.key)=\(.value)"
+            ' \
+          | tee -a "$GITHUB_OUTPUT" # assumes no secrets are passed in as inputs, as they're printed by tee!
+      # ... do something with the output (example):
+      - name: Some step using an input
+        run: |
+          # Assumes the building block definition has an input called 'github_handle'
+          echo '${{ steps.decodeBuildingBlockInputs.outputs.github_handle }}'
+```
 
 ### Status Updates