Right now we deploy on the following moments:
- automatically on push to master, to staging env
- via workflow_dispatch on master, to production env
- via responding
deploy on a PR, to develop
I propose to do the following:
- automatically on push to master, to staging env
- via workflow_dispatch on any branch, to any env
This way, we can have multiple branches active and allow them all to be deployed to master if we want it. I think that for the purpose of this project, where we sometimes might want to make changes to thadmin for a specific event, this is desirable. Github offers a nice UI for this, too (when triggering a workflow, you can specify the branch you want to use, and you can select multiple env's to deploy to)
Right now we deploy on the following moments:
deployon a PR, to developI propose to do the following:
This way, we can have multiple branches active and allow them all to be deployed to master if we want it. I think that for the purpose of this project, where we sometimes might want to make changes to thadmin for a specific event, this is desirable. Github offers a nice UI for this, too (when triggering a workflow, you can specify the branch you want to use, and you can select multiple env's to deploy to)