conda-forge / conda-forge/conda-forge-bot
Apply all migrators immediately when a new feedstock is created?
- Dominant language
- Python
- Stars
- 76
- Forks
- 99
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 126
Description
This is related to an issue that we encountered when creating cusparselt-feedstock.
It builds only on CUDA 11.0 (and runs on 11.x), which is currently under migration. So, when the feedstock was created, the entire package was empty and no package was generated and uploaded, making me mistakenly think we need to have a custom `conda_build_config.yaml` (which we removed when it was still in the stage-recipe), so I did so. But then in about an hour or two, the bot issued a bunch of migration PRs that would have resolved the problem for me.
My question is:
1. Is it possible for the bot to rerender the feedstock at its generation time by taking into account all ongoing migrators, as if it's done locally with a valid `meta.yaml` etc?
2. If 1 is not possible, then is it possible to kick off the migration bot at the generation time, so that we don't have to wait those migration PRs for ~1 hour, but instead get them immediately after the feedstock is created and is in a valid state?
Addressing either 1 or 2 would lead to a better maintainer experience IMHO. Thanks!
cc: @jakirkham who witnessed my silliness 😅
Contributor guide
Assessment
This issue has not been assessed yet.