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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conda recipe #404
Conda recipe #404
Changes from all commits
c83ad7a
c20af12
5066e4a
1f3a405
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just in case it's a hassle for you to change this manually. Now that we have the version within the file
VERSION
, would it be handy to have a very simple python script that replaces this bit of version in themeta.yaml
, triggered by a GitHub action?For example, something like the following, summarised by our friend GPT:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, only if it's less of a hassle to keep in mind that the VERSION is also in the YAML file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or actually, rather than modify this YAML file, why not have the other files read the file
meta.yaml
instead ofVERSION
? That way, the version exists only in one place. We could use a regex to find the version within this yaml file and extract it insteadThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's okay for now, but it's something to keep in mind for a future PR (e.g. in #406)... we can decide the direction of information flow (i.e. from VERSION to YAML or vice versa) and how it's triggered there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why these requirements have to be present in both
host
andrun
sections, but it's the only way I could get it to work...