-
Notifications
You must be signed in to change notification settings - Fork 61
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
chore(ci): trigger nextstrain/docker-base rebuild on release #1505
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How do we test that? |
I guess we can just wait and see whether ti works on next release |
68d6b2b
to
2a1cbe8
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.
This rebuild was triggered by the new workflow. Looks good. Let's check if the release trigger works as expected during the next release.
I've force-pushed to drop 9bd5fc5. Feel free to reword or squash b1aa56a into your other commit.
The activity type released¹ more directly matches the desire here: > A release was published, or a pre-release was changed to a release. ¹ <https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=released#release>
2a1cbe8
to
c6e3258
Compare
Resolves #652
Other changes made:
GH_TOKEN_NEXTSTRAIN_BOT_WORKFLOW_DISPATCH