Fix development status in setup.cfg#3550
Merged
freddyaboulton merged 2 commits intomainfrom Jun 9, 2022
Merged
Conversation
freddyaboulton
requested review from
christopherbunn,
chukarsten,
fjlanasa and
stefaniesmith
Codecov Report
@@ Coverage Diff @@
## main #3550 +/- ##
=====================================
Coverage 99.7% 99.7%
=====================================
Files 335 335
Lines 33252 33252
=====================================
Hits 33123 33123
Misses 129 129 Continue to review full report at Codecov.
|
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Lol the setup.cfg broke pypi upload after all @jeremyliweishih 😆 (https://github.com/alteryx/evalml/runs/6819120384?check_suite_focus=true)
Verified the new status works on test pypi: https://test.pypi.org/project/evalml-freddy/0.53.1/#history
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.