-
Notifications
You must be signed in to change notification settings - Fork 398
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
Docs: Migration notebook suggestions #4996
Docs: Migration notebook suggestions #4996
Conversation
…ame-argilla-to-argilla-v1
…gilla/define-new-argilla-package-and-move-argilla-to-argilla-v1
…ine-new-argilla-package-and-move-argilla-to-argilla-v1
<!-- Thanks for your contribution! As part of our Community Growers initiative 🌱, we're donating Justdiggit bunds in your name to reforest sub-Saharan Africa. To claim your Community Growers certificate, please contact David Berenstein in our Slack community or fill in this form https://tally.so/r/n9XrxK once your PR has been merged. --> # Description This PR is part of the work to tackle #4889. The current package `argilla-sdk` has been renamed to `argilla`. Once the rest of the open PRs are merged, I will bring all those changes here and rename the project folder `argilla-sdk` to `argilla` **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [ ] Test A - [ ] Test B **Checklist** - [ ] I added relevant documentation - [ ] I followed the style guidelines of this project - [ ] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I filled out [the contributor form](https://tally.so/r/n9XrxK) (see text above) - [ ] I have added relevant notes to the `CHANGELOG.md` file (See https://keepachangelog.com/)
We probably want to do something better for the predictions -> suggestions in |
I see we're not providing a solution for TokenClassification > SpanQuestion and Text2Text > TextQuestion. I assume that's because of their minimal use @frascuchon ? |
@frascuchon @nataliaElv I would like to move this notebook into a markdown based guide like the other how-to?. That would allow me to do these steps:
@nataliaElv If that's ok for you, I'll create a PR off this? |
Sure! Go ahead. Or you can even use this PR to make those changes if that's easier for branch/PR management. |
Thanks for this @nataliaElv. I will close this PR in favor of #5002 |
Argilla Community Growers
Thanks for your contribution! As part of our Community Growers initiative 🌱, we're donating Justdiggit bunds in your name to reforest sub-Saharan Africa. To claim your Community Growers certificate, please contact David Berenstein in our Slack community or fill in this form https://tally.so/r/n9XrxK once your PR has been merged.
Pull Request Templates
Please go the the
Preview
tab and select the appropriate sub-template:Generic Pull Request Template
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Closes #<issue_number>
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)
How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference
tests
)Checklist