Github Actions workflow for automated release deployment

[acrenw]

CI/CD: Deployment into universal-gestures-release

https://www.notion.so/uwrl/11ebc072402f81feb5d7f13de9ea5b56?v=11ebc072402f81bba16f000c709aebde&p=137bc072402f807f8282e8b1b27e30f1&pm=s

Summary of Changes

• Added a yaml file for Github Action workflows
• Uses workflow_dispatch so updates are ran manually by pressing "Run workflow"

Screenshots of Changes to Scenes/Prefabs

N/A

[JustinLin905]

This looks really cool! One question I have is with the scope of the files this automated workflow grabs. We only want files in the Assets and Samples~ folder to be pushed to the universal-gestures-release repo. Do you know if your solution accommodates this? There is a risk that if someone changes some other file in the dev repo, it could be recognized as changed, and be pushed into the release repo even though it's not wanted. Check out the universal-gestures-release repo: we want to maintain that very clean file structure, without adding any unwanted files :) thanks Cera

[acrenw]

This looks really cool! One question I have is with the scope of the files this automated workflow grabs. We only want files in the Assets and Samples~ folder to be pushed to the universal-gestures-release repo. Do you know if your solution accommodates this? There is a risk that if someone changes some other file in the dev repo, it could be recognized as changed, and be pushed into the release repo even though it's not wanted. Check out the universal-gestures-release repo: we want to maintain that very clean file structure, without adding any unwanted files :) thanks Cera

Hi sorry I don't think I see a Samples~/ folder in universal-gestures-unity so right now I only changed it to detect changes in the Assets/ folder, is that okay?