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

pypi: move from pushing a test release every MR to pushing only on tag #97

Merged
merged 1 commit into from
Dec 5, 2023

Conversation

thinkl33t
Copy link
Contributor

No description provided.

@thinkl33t thinkl33t requested a review from jonathanmaw December 5, 2023 14:29
Copy link
Contributor

@jonathanmaw jonathanmaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I was briefly concerned that there's no value to running a test deployment and then the real deployment immediately after, but https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions#jobs is clear that job steps depend on previous steps, so this is a way to cleanly catch a deployment failure.

Approved!

@thinkl33t thinkl33t merged commit e0e655b into main Dec 5, 2023
7 checks passed
@thinkl33t thinkl33t deleted the bobclough/package-release-attempt-2 branch December 5, 2023 15:26
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