run: Resolve workflow names using pathogen registration, if available#481
Merged
run: Resolve workflow names using pathogen registration, if available#481
Conversation
This decoupling of workflow names from paths was always expected and intended to be possible, and now it is. Related-to: <nextstrain/zika-tutorial#19> Related-to: <nextstrain/public#1>
tsibley
force-pushed
the
trs/resolve-pathogen-workflow-path
branch
from
5410d79 to
8d39d01
Compare
joverlee521
added a commit
to nextstrain/zika-tutorial
that referenced
this pull request
Sep 30, 2025
joverlee521
approved these changes
Sep 30, 2025
Contributor
joverlee521
left a comment
joverlee521
left a comment
There was a problem hiding this comment.
Thanks! Works as expected with nextstrain/zika-tutorial@e93e1a6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This decoupling of workflow names from paths was always expected and intended to be possible, and now it is.
Related-to: nextstrain/zika-tutorial#19
Related-to: nextstrain/public#1
Checklist