-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add workflows that are not directly using pathogen-repo-build
#12
Comments
Ah right, just remembered this issue since I changed avian flu GH Action workflows in nextstrain/avian-flu#71 but the name is I'm going to add a separate check for the avian-flu workflow, but other pathogens that only use NCBI data should continue to follow the generic |
Or maybe just update exact match to pattern match diff --git a/pathogen-workflows.sql b/pathogen-workflows.sql
index d68d368..cf23d33 100644
--- a/pathogen-workflows.sql
+++ b/pathogen-workflows.sql
@@ -93,7 +93,7 @@ workflow as materialized (
*
* <https://github.com/nextstrain/status/issues/12>
*/
- or path = '.github/workflows/ingest-to-phylogenetic.yaml')
+ or path like '.github/workflows/ingest-to-phylogenetic%.yaml')
and name != 'CI'
), |
@joverlee521 it looks like, reviewing the above, that the work here is done and this issue can be closed? |
Ah yeah, I'll consider #24 good enough. We can re-open this if there are other cases not supported. |
Context
Prompted by nextstrain/zika#55 (comment)
We want to monitor GH Action workflows using the
pathogen-repo-build
reusable workflow and we are currently filtering for them withstatus/pathogen-workflows.sql
Lines 87 to 88 in d744ff7
However, this does not include workflows that are nesting reusable workflows, such as the current zika ingest-to-phylo.yaml workflow.
Possible solutions
ingest-to-phylogenetic.yaml
pathogen-repo-build
workflow. (GH Action currently allows four levels of nested reusable workflows)The text was updated successfully, but these errors were encountered: