raulcd commented on PR #14102: URL: https://github.com/apache/arrow/pull/14102#issuecomment-1246505954
Thanks for the detailed response! > Yes of course. This comes from more or less 1:1 from the so-called [feedstock](https://github.com/conda-forge/arrow-cpp-feedstock) on the conda-forge side (though in this case it's still the state of a [PR](https://github.com/conda-forge/arrow-cpp-feedstock/pull/848)), where the recipe is maintained, and where all these `.ci_support/*.yaml` files get generated based on the recipe & the conda-forge global [pinning](https://github.com/conda-forge/conda-forge-pinning-feedstock) by our friendly automation bots. This `.ci_support/*.yaml` are updated with `conda smithy rerender`? Is this done with the automation bots or is this done on a periodic basis? I understand we should not do it in the arrow repo as we should just pull the upstream feedstock ones. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
