Note to ourselves: we should make the PyPi (and conda-forge) publishing be automatically triggered from a CI step in github, once the repo is tagged with something like `vX.Y.Z`. #96
We should make the PyPi (and conda-forge) publishing be automatically triggered from a CI step in github, once the repo is tagged with something like vX.Y.Z.
It would ensure pip+conda releases are always consistent with the code on github (and make the whole release process much easier -- just tag, push & let the CI do the rest).
We should make the PyPi (and conda-forge) publishing be automatically triggered from a CI step in github, once the repo is tagged with something like
vX.Y.Z.It would ensure pip+conda releases are always consistent with the code on github (and make the whole release process much easier -- just tag, push & let the CI do the rest).
Originally posted by @mjuric in https://github.com/matthewholman/assist/issues/94#issuecomment-1810720823