I've got a sinking feeling

Author: PathogenDavid

.github/workflows/workflow_run_sink.yml

@@ -11,8 +11,14 @@ jobs:
       - run: cat <<< "$heck"
         env:
           heck: ${{toJSON(github.event)}}
+      # I was wondering why this example here uses actions/github-scripts
+      # https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#using-data-from-the-triggering-workflow
+      # And it turns out that stupid download-artifact ignores the run-id unless you explicitly provide a token
+      # https://github.com/actions/download-artifact/blob/d3f86a106a0bac45b974a628896c90dbdf5c8093/src/download-artifact.ts#L53
+      # We can just manually specify our token though, the documentation of download-artifact says it defaults to the run token but it doesn't actually
       - uses: actions/download-artifact@v4
         with:
           run-id: ${{github.event.workflow_run.id}}
           name: test-artifact
+          github-token: ${{github.token}}
       - run: cat output.txt

.github/workflows/workflow_run_source.yml

@@ -1,4 +1,7 @@
 # https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_run
+# There is unfortunately not any sort of feedback on the source workflow that a sink workflow was triggered or what its status is.
+# The sink will be marked as having been triggered by whoever triggered this workflow, but it does not show the orginal tirgger reason (IE: push to `main2`)
+# It also doesn't give you a link back to the triggering workflow or anything either, which is pretty lame.
 name: workflow_run source
 on:
   push: