Closed ZenSorcere closed 3 years ago
IT's possible we might need to adjust the yml file at the top from "push" to "merge" for what we are looking to trigger?
IT's possible we might need to adjust the yml file at the top from "push" to "merge" for what we are looking to trigger?
According to anouther website, the "push" at the beginning should be fine. Quote from that website: "I have the workflow set to run when something is committed to the main branch. So if I merge a PR or commit straight to main it will kick off a build and deploy"
we may want to reference this website (github actions and deploying to S3) as this yml file referenced has some additional elements that might be needed.
This attempts to address Issued #142 (implement Github actions to automate deploying to S3 bucket). I'm not linking the issue to this PR as this needs to be merged to see if Issue 142 might be closeable.
Following the instructions put forth here, I have created a main.yml file in a new directory: .github/workflows/.
To see if this works:
This PR will need the yml file updated and the secrets added to the repo and then could potnetially be merged to main.
At that point, a test merge to main would be needed, to see if an auto-deploy actually occurs. If not, then additional work will be needed.