Isuru Fernando comments

Results 928 comments of


                                            Isuru Fernando

Change how `default` as a CI provider points at actual providers

Ah, so the feedstock config file remains the same?

Change how `default` as a CI provider points at actual providers

Thanks for clarifying. I'm okay with releasing conda-smithy just to make this change.

Change how `default` as a CI provider points at actual providers

That's unrelated. ppc64le builds are not running right now because we ran out of credits in Travis.

Change how `default` as a CI provider points at actual providers

We can already do that by changing https://github.com/conda-forge/conda-smithy/blob/main/conda_smithy/configure_feedstock.py#L1852-L1862

add .smithy-versions.json file to feedstocks

@dougalsutherland, what are the benefits of doing this?

add .smithy-versions.json file to feedstocks

> Is there a strong reason to obfuscate it? Having a bunch of data in the feedstock that changes every time a person does a rerender is very distracting to...

run conda render prior to build

conda render is done in 3 places now. First in `conda render` call, then in `conda build` call and at last in `upload` call. Can we reduce it to at...

run conda render prior to build

3rd one is at https://github.com/conda-forge/conda-forge-ci-setup-feedstock/blob/a1026adb523b6562c16329170e7e304a25ed4033/recipe/conda_forge_ci_setup/upload_or_check_non_existence.py#L111

run conda render prior to build

@minrk, can you send a PR to conda-forge-ci-setup-feedstock to print the rendered recipe there?

Add `.vscode` folder to feedstock `.gitignore` file

Should we add files for other IDEs as well? Or none at all?