-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy Docker image to ghcr.io #579
Conversation
2e3eb73
to
8a3f381
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it does not make sense to run CI on the master branch if you are not evaluating test coverage for the branch or other specific metrics. Running linters is also unnecessary when they are already executed on every commit of a pull request.
In my opinion, deployments should be handled separately and triggered either by a push to the master branch or manually using workflow_dispatch
I added a conclusion job, which is not super pretty, but often a requirement if one wants to get GitHub Actions to work well with both pull request and merge queue workflows.. Anyway, looks like it behaves like I wanted it to now. |
This changes the deployment from a webhook to a docker push to the ghcr.io registry. It also switches to merge queues.