-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Can we fully automate packages' new releases? #25591
Comments
You may like to review the configuration options here: https://conda-forge.org/docs/maintainer/conda_forge_yml/#bot . For example, you may consider editing bot:
automerge: true
inspection: update-grayskull If you look at the results of this search, you will see, for example, that this is done in the great-expectations feedstock It may also be helpful to review https://conda-forge.org/docs/maintainer/infrastructure/#automerge |
Thank you @cameronraysmith, so there are two ways to add automerge:
What's the relationship between them? Are they the same thing, or both need to be done before automerge is enabled? Is there any case when automerge wouldn't go through? |
https://conda-forge.org/docs/maintainer/conda_forge_yml/#bot is the best reference I am aware of regarding the topic of your OP |
General comment:
@conda-forge/staged-recipes
@conda-forge/help-python
I'm exploring ways to automate the conda-forge releases of my packages. I see that there's a bot, but it looks like it may not work if the dependency changes. Is it impossible to avoid manual effort entirely here?
In the process of looking for references I see that pandas uses a different bot to update the package (not sure how to do that), but still requires manual approval, and in some cases, manual changes (example). I suppose if automation is possible, pandas would have done it, but maybe I'm missing something.
If this isn't the right forum to ask this question, please let me know who is the right point of contact. Thanks for your help!
The text was updated successfully, but these errors were encountered: