-
Notifications
You must be signed in to change notification settings - Fork 1
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
Copier update #302
Copier update #302
Conversation
37163fd
to
90be93a
Compare
conda/meta.yaml
Outdated
@@ -32,6 +30,7 @@ test: | |||
imports: | |||
- beamlime | |||
requires: | |||
<<<<<<< before updating |
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.
This needs to be fixed.
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.
Good catch!
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.
Maybe we need a rule to trigger conda builds in CI when certain files like meta.yaml
have changed?
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.
Maybe we need a rule to trigger conda builds in CI when certain files like meta.yaml have changed?
Yeah maybe but if we do move to conda-forge for all our packages no need to worry about that? As for pure python packages conda-forge would just use pypi to build for conda.
No description provided.