-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Sklearn decisiontree #23007
Sklearn decisiontree #23007
Conversation
Thanks for contributing to Ivy! 😊👏 |
…/ivy into sklearn-decisiontree
Co-authored-by: umairjavaid <[email protected]>
Co-authored-by: umairjavaid <[email protected]> Co-authored-by: Gadri Ebenezer <[email protected]> Co-authored-by: nathzi1505 <[email protected]> Co-authored-by: muzakkirhussain011 <[email protected]> Co-authored-by: AliTarekk <[email protected]> Co-authored-by: ivy-branch <[email protected]> Co-authored-by: Shreyansh Bardia <[email protected]> Co-authored-by: Vaatsalya <[email protected]> Co-authored-by: Akshay <[email protected]> Co-authored-by: ReneFabricius <[email protected]> Co-authored-by: Vaibhav Deshpande <[email protected]> Co-authored-by: Vaibhav Deshpande <[email protected]> Co-authored-by: Jomer Barcenilla <[email protected]> Co-authored-by: Nripesh Niketan <[email protected]> Co-authored-by: Kareem Morsy <[email protected]> Co-authored-by: Lucas Alava Peña <[email protected]> Co-authored-by: Sai-Suraj-27 <[email protected]> Co-authored-by: Sulaiman Mutawalli <[email protected]> Co-authored-by: RashulChutani <[email protected]> Co-authored-by: Moses Daudu <[email protected]> Co-authored-by: Ahmed Hisham <[email protected]> Co-authored-by: AnnaTz <[email protected]> Co-authored-by: Indraneel kumar <[email protected]> Co-authored-by: hirwa-nshuti <[email protected]> Co-authored-by: Javeria-Siddique <[email protected]> Co-authored-by: Peter Kiprop <[email protected]> Co-authored-by: Humza Tareen <[email protected]> Co-authored-by: Nitesh Kesharwani <[email protected]> Co-authored-by: Bhushan Srivastava <[email protected]> Co-authored-by: hmahmood24 <[email protected]> Co-authored-by: Daniel4078 <[email protected]> Co-authored-by: Mostafa Hani <[email protected]> Co-authored-by: Mostafa Hany <[email protected]> Co-authored-by: Vismay Suramwar <[email protected]> Co-authored-by: Eddy Oyieko <[email protected]> Co-authored-by: Madjid Chergui <[email protected]> Co-authored-by: Mohammed Ayman <[email protected]> Co-authored-by: akshatvishu <[email protected]> Co-authored-by: MahmoudAshraf97 <[email protected]> Co-authored-by: Yusha Arif <[email protected]> Co-authored-by: KHETHAN <[email protected]> Co-authored-by: khethan123 <[email protected]> Co-authored-by: NripeshN <[email protected]> Co-authored-by: Aaryan562 <[email protected]> Co-authored-by: Ario Zareinia <[email protected]> Co-authored-by: MahadShahid8 <[email protected]> Co-authored-by: Dharshannan Sugunan <[email protected]> Co-authored-by: RickSanchezStoic <[email protected]> Co-authored-by: Abdurrahman Rajab <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our contributing guide and our PR template.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
Conventional Commit PR Title
In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:
- docs: correct typo in README
- feat: implement dark mode"
- fix: correct remove button behavior
Linting Errors
- Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
- No subject found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all changes other than the ones in the ivy/frontends/sklearn
and the ivy_tests/test_ivy/test_frontends/test_sklearn
folders can be reverted as they seem unrelated. Thanks @umairjavaid 😄
PR Description
Related Issue
Close #
Checklist
Socials: