update prepare_recipe_in_local_feedstock() to copy over recipe from repo to fake feedstock #82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tarts with 'for_release'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
updated prepare_recipe_in_local_feedstock_repo() to check if branch starts with "for_release_".
if so, the branch has recipe/meta.yaml.in that has been updated with url and sha256 for the release, and the recipe
can be just copied over to the fake feedstock. (this is only for building non conda-forge package).
This for_release branch does not get merged to the master branch of the project though, just use it for building a release package.
We need to come up with a better way.
also add copying migrations/hdf51106.yaml file from repo dir to fake feedstock, this is needed for building non conda-forge package.