This might be possible by configuring actions/download-artifact to use pattern matching along with adding a step to ResearchDataCom/actions/pre-commit (which every CI workflow runs first) that generates a dummy artifact. This would require consistent naming conventions across composite workflows for artifacts containing dependency pins. The name and contents of the dummy artifact would need to be a sentinel value and thus extremely unlikely to conflict with or cause problems for our current (or future) development tooling.
Refer to ResearchDataCom/templates#6 and actions/download-artifact#352 for additional context.
This might be possible by configuring actions/download-artifact to use pattern matching along with adding a step to ResearchDataCom/actions/pre-commit (which every CI workflow runs first) that generates a dummy artifact. This would require consistent naming conventions across composite workflows for artifacts containing dependency pins. The name and contents of the dummy artifact would need to be a sentinel value and thus extremely unlikely to conflict with or cause problems for our current (or future) development tooling.
Refer to ResearchDataCom/templates#6 and actions/download-artifact#352 for additional context.