This adds GitHub workflows that will trigger docker builds (no pushes) on merge group events (which fire off when we enable merge queues for PR's). The workflows are slimmed down versions of the build and push workflows that run on tag events.
So far, just doing backend and web, model server might be next.
This is following a pattern in Github's docs about this feature which checks against both pull requests on submission as well as when being integrated by the merge queue into main. Thoughts on if we want to limit this to the merge queue only? Some googling suggest this is possible with a bit of magic syntax.
This adds GitHub workflows that will trigger docker builds (no pushes) on merge group events (which fire off when we enable merge queues for PR's). The workflows are slimmed down versions of the build and push workflows that run on tag events.
So far, just doing backend and web, model server might be next.
This is following a pattern in Github's docs about this feature which checks against both pull requests on submission as well as when being integrated by the merge queue into main. Thoughts on if we want to limit this to the merge queue only? Some googling suggest this is possible with a bit of magic syntax.
https://stackoverflow.com/questions/76655935/when-does-a-github-workflow-trigger-for-merge-group-and-is-it-restricted-by-bran