When conda-forge package is merged/up on anaconda.org rever:
Restarts a webservice
Sends out a tweet about the new release (with changelog?)
Updates the ghrelease to note that the package is up on conda-forge
Sends an email to the user mailing list that the new package is up
My current thinking on this would to have rever either a) start a daemon process which looks at the conda-forge PR and awaits it's merge, b) doesn't return but keeps running in the background awaiting the merge of the PR and finally returns when all the activities downstream of conda-forge are done.
Use Case:
My current thinking on this would to have rever either a) start a daemon process which looks at the conda-forge PR and awaits it's merge, b) doesn't return but keeps running in the background awaiting the merge of the PR and finally returns when all the activities downstream of conda-forge are done.