It might not be done here - but I think it's worth also exploring when database migrations happen as part of CD, not sure if this currently a manual process?
Are you willing to contribute to developing this feature?
✅ Yes, me or my team intend to do the development.
Is there an existing issue for this?
Is your proposal related to a problem or functionality gap?
Currently the release workflow for dev/test/production is 3 separate Github actions, working with Gitflow. So merging a new fix requires 3 separate PRs, artifacts, and deployments: https://github.com/Health-Informatics-UoN/CaRROT-Mapper/pulls?q=is%3Apr+is%3Aclosed
Describe your proposal
I propose combining this into one workflow, utilising Github environments to deploy a single artifact from the main branch. An example here: https://github.com/Health-Informatics-UoN/rcc-monitor/actions/runs/7931015704
Describe alternatives you've considered
No response
I'm part of a Project Team
Yes - DRS
Anything else?
It might not be done here - but I think it's worth also exploring when database migrations happen as part of CD, not sure if this currently a manual process?
Are you willing to contribute to developing this feature?
✅ Yes, me or my team intend to do the development.