Skip to content
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

Configure dev releases #26

Merged
merged 2 commits into from
Mar 12, 2018
Merged

Conversation

jakirkham
Copy link
Member

Configures the newly created dev branch to publish to a dev label as opposed to main under the conda-forge channel.

cc @jlstevens

also cc-ing @CJ-Wright @isuruf (for awareness)

As this is now making a `dev` release, set the label to `dev` instead of
`main` so that users have to opt-in to getting this release.
Now that this feedstock is configured to upload to a different label,
re-render so that the CI scripts actually upload to this other label.
@jakirkham
Copy link
Member Author

Skipped CI as it is irrelevant for these changes. Of course CircleCI doesn't care we told it to skip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant