Terminate AppVeyor if a package is in the channel about conda-forge.github.io HOT 4 CLOSED

In a feedstock or in staged-recipes? The latter is a quick win, but the former is kind of questionable IMO.

from conda-forge.github.io.

but the former is kind of questionable IMO.

Because one would have to always build the build number to see a build happening?

from conda-forge.github.io.

Because one would have to always build the build number to see a build happening?

If you've made a change to the feedstock but not bumped the build number, you still want to know it works, even if you don't want a new binary. Checking upfront to determine whether to do the work brings us back to one of the major issues with multi-recipe repositories (the fact that you have to look for whether a recipe need building or not).

I'm not sure we are going to be able to do anything about that (other than by upgrading AppVeyor [I've started a conversation with them, and will let you know if anything comes of it])

from conda-forge.github.io.

If you've made a change to the feedstock but not bumped the build number, you still want to know it works, even if you don't want a new binary.

I get that. I just thought that this would be a minor problem than re-starting everything.

I'm not sure we are going to be able to do anything about that (other than by upgrading AppVeyor [I've started a conversation with them, and will let you know if anything comes of it])

That works too 😄

from conda-forge.github.io.