PR #20 contains the necessary updates to rever.xsh to perform the two-step release procedure of this package on GitHub followed by conda-forge (necessarily in that order).
After the merge, someone logged in under the Billingegroup should run rever 0.1.0 (or replacing "0.1.0" with whatever version number feels appropriate) in the root directory of the project to release it on GitHub which is a necessary precursor step to the conda-forge release.
PR #20 contains the necessary updates to rever.xsh to perform the two-step release procedure of this package on GitHub followed by conda-forge (necessarily in that order).
After the merge, someone logged in under the Billingegroup should run
rever 0.1.0(or replacing "0.1.0" with whatever version number feels appropriate) in the root directory of the project to release it on GitHub which is a necessary precursor step to the conda-forge release.