Get CI working again on this repo

[sbillinge]

No description provided.

[rozyczko]

As mentioned in the PR comments:
diffpy/diffpy.structure#56 (comment)
we have a working GitHub workflow for pdffit2 (not Travis!)

I will clean it up and make a pull request.
Currently, we have a step which uploads the artefacts to a local pypi repo, which needs to be replaced with a proper (twine) upload to the main pypi channel, with correct credentials.

[sbillinge]

that's perfect, thanks! Sorry for the confusion, I was seeing travis ymls and was assuming this was it, but they may be hanging around from stuff we did before. I would love to see that PR. btw, we are also working on releasing all of the diffpy stack on conda-forge, but having it more or less automatically available on pypi is great. Thank you so much for your contributions! S

…

On Thu, Feb 23, 2023 at 9:37 AM Piotr Rozyczko ***@***.***> wrote: As mentioned in the PR comments: diffpy/diffpy.structure#56 (comment) <diffpy/diffpy.structure#56 (comment)> we have a working GitHub workflow for pdffit2 (not Travis!) I will clean it up and make a pull request. Currently, we have a step which uploads the artefacts to a local pypi repo, which needs to be replaced with a proper (twine) upload to the main pypi channel, with correct credentials. — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAOWUMPBOY3TC6MRA2YLYDWY4OS5ANCNFSM5YXHCKTQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Simon Billinge Professor, Columbia University

[sbillinge]

This fix was merged, but we have removed the build.yml in cookiecuttering. But this PR is super-useful. @Sparks29032 @8bitsam it would be good to have a quck convo about this and whether we want to adopt any of it in our cookicutter. In particular, doing prereleases so we don't have lots of minor release bumps hanging around while we debug releases....