You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Appears you add a 'service' to a github action job which in this case is mysql. Then you define the credentials and config. This repo appears to be an official github example page: https://github.com/actions/virtual-environments
The next step in #49 is to run all the tests a second time using the mysql database rather than just a sqlite in memory database.
It appears possible and relatively straightforward to include mysql to a github action workflow.
Found this blog post on the process:
https://freek.dev/1590-how-to-use-a-mysql-database-on-github-actions
Appears you add a 'service' to a github action job which in this case is mysql. Then you define the credentials and config. This repo appears to be an official github example page:
https://github.com/actions/virtual-environments
In particular this template for postgres looks helpful:
https://github.com/actions/example-services/blob/main/.github/workflows/postgres-service.yml
it appears we would do something like this:
However just found this announcement:
https://github.blog/changelog/2020-02-21-github-actions-breaking-change-ubuntu-virtual-environments-will-no-longer-start-the-mysql-service-automatically/
Which may mean that it instead done via a step. Unsure how this would work with a windows container though
The text was updated successfully, but these errors were encountered: