Skip to content

Skip the "test" stage when making a release #3908

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

Merged
merged 1 commit into from
Aug 29, 2018

Conversation

nicoddemus
Copy link
Member

Given that our guidelines demand that the CI have already passed, it seems
wasteful to run all those jobs again for the exact same commit.

As discussed in #3906 (comment),
this will skip the "test" stage when building a tag for deployment.

Given that our guidelines demand that the CI have already passed, it seems
wasteful to run all those jobs again for the exact same commit.

As discussed in pytest-dev#3906 (comment),
this will skip the "test" stage when building a tag for deployment.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 92.238% when pulling 3ca7069 on nicoddemus:optimize-release into d76fb83 on pytest-dev:master.

@nicoddemus nicoddemus merged commit 338953a into pytest-dev:master Aug 29, 2018
@nicoddemus nicoddemus deleted the optimize-release branch August 29, 2018 21:53
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.

4 participants