fix: Fix PsiTurk release location

[RobertGemmaJr]

• PsiTurk build is now uploaded to the GitHub release it belongs to
• The PsiTurk build is folder is zipped before being uploaded

[github-actions]

Visit the preview URL for this PR (updated for commit c4a627a):

https://ccv-honeycomb--pr351-ref-psiturk-release-938ozvdb.web.app

_{(expires Mon, 18 Dec 2023 16:00:49 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 4ace1dcea913a952d2a1af84b94a4421bf36e610}

[RobertGemmaJr]

[This is my reminder to create a new release once this is merged to confirm the action works]

[eldu]

I did a whole bunch of reading on uploading artifacts 😵 Looks like you wanted to add the artifacts onto the tags !

Quick question:

So this action runs on

# Runs the build and package scripts when a new tagged release is publishe, created or edited
# Note that this runs for both releases and pre-releases: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release
on:
  release:
    types: [created, edited, published]

I assume when a release is created, there is a tag that is also created?

Does in line 179 tag: ${{ github.ref }} refer to the correct tag when the release is edited or published?

Commenting for now... with questions.

[RobertGemmaJr]

I assume when a release is created, there is a tag that is also created?

Does in line 179 tag: ${{ github.ref }} refer to the correct tag when the release is edited or published?

@eldu So, yes, our current instruction is for folks to create a new tag whenever a new release is created. github.ref refers to the tag of the release that triggered the workflow. It will always refer to the correct release although tbh I'm unsure what it will do when file artifacts are already present in the release. I think it will overwrite naming conflicts but I haven't full tested that