-
Notifications
You must be signed in to change notification settings - Fork 11
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
Standardize pathogen-repo-ci use across pathogen repos #84
Comments
I'm a bit out of the loop here. What's the difference between mpox's CI (which uses |
Yup, the use of the |
Related/precursor work: #89 |
Ideas here came out of discussion with @tsibley in our 1:1 regarding #62 (comment). This would supersede #63 + #62.
Proposal
With the standardization of pathogen repos following the pathogen-repo-guide, we can now enforce the standardized use of the
pathogen-repo-ci
workflow.In order to use the centralized
pathogen-repo-ci
, a pathogen repo will need to meet two requirements.follow a strict repo organization (currently required to have a
phylogenetic
subdirectory)use a standard mechanism for specifying the CI build, e.g. use a standard CI config that can be specified with
This would simplify each pathogen repo's CI workflow to:
Then the docker-base/conda-base CIs can be simplified to just matrix of pathogen repos instead of needing to pass in additional build args.
Concrete steps
pathogen-repo-ci
#93pathogen-repo-ci
#94The text was updated successfully, but these errors were encountered: