TEMP: Dependencies: Use pycaret-next#844
Draft
amotl wants to merge 1 commit into
Draft
Conversation
amotl
force-pushed
the
pycaret-next
branch
3 times, most recently
from
7c12531 to
d88e424
Compare
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
1 participant
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.
Please do not merge.
About
Validate pycaret-next on the test suite 1 on CI/GHA.
References
Thanks, @celestinoxp!
Footnotes
The test suite mean it is mostly invoking Jupyter Notebooks and checks if they run to completions. There are no other more specific or detailed software tests here, it's effectively just another little item that could be used as a compatibility indicator that may be useful when approaching pycaret-next. ↩