Skip to content
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

Add manually-triggerable GitHub Action workflows for publishing to PyPI #140

Merged
merged 1 commit into from
Jan 23, 2021

Conversation

jpgill86
Copy link
Collaborator

We will be able to run these workflows manually from the GitHub Actions page. For now, until I grow to trust it, I prefer triggering manually rather than on pushing a tag. Perhaps after the next release I will feel comfortable with it. 😁

@samuelgarcia, I think only you will be able to add the PyPI secret tokens to this repo. We are co-maintainers of the official PyPI project, but only I am a maintainer of the TestPyPI project (I could add you if you like; you may need to create an account first). So, I've taken the initiative to generate tokens for both projects. I will email them to you so that you can add them to this repo's GitHub secrets settings.

@jpgill86 jpgill86 added this to the 1.4.1 milestone Jan 23, 2021
@jpgill86 jpgill86 merged commit 768c491 into NeuralEnsemble:master Jan 23, 2021
@jpgill86 jpgill86 deleted the gh-actions-publish-pypi branch January 23, 2021 06:32
@samuelgarcia
Copy link
Collaborator

bien joué!
Is the pypi test usefull ?

@jpgill86
Copy link
Collaborator Author

jpgill86 commented Jan 26, 2021

Is the pypi test usefull ?

I like to publish to TestPyPI first to make sure the project page renders correctly. It's probably not necessary if no changes were made to the README or setup.py, but I still like to make sure it works.

Any luck with adding to GitHub the API tokens that I emailed to you so that we can make use of these workflows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants