Disable monkeypox CI until pathogen-repo-ci supports custom build directories See issue https://github.com/nextstrain/.github/issues/63

[corneliusroemer]

Disable monkeypox CI until pathogen-repo-ci supports custom build directories

See issue nextstrain/.github#63

Fixes augur CI failures

[victorlin]

(copied from Slack)

I don't think disabling monkeypox CI (not only necessary now in Augur, but also docker-base, conda-base) is an acceptable trade-off to use the new pathogen template. I'd vote to revert nextstrain/mpox#198 until pathogen-repo-ci is updated to work with the new template.

[joverlee521]

I just remembered that this CI workflow is actually not even using the pathogen-repo-ci because we are testing the local version of Augur

augur/.github/workflows/ci.yaml

Lines 74 to 76 in 7cb3848

	# TODO: Use the central pathogen-repo-ci workflow¹. Currently, this is not
	# possible because it only supports "stock" docker and conda runtimes.
	# ¹ https://github.com/nextstrain/.github/blob/-/.github/workflows/pathogen-repo-ci.yaml

Leaving as-is for now as we figure out the standard repo organization and decide if we want to make sweeping changes, but we should resolve nextstrain/.github#66 so that we don't have to maintain this CI workflow separately.