-
Notifications
You must be signed in to change notification settings - Fork 390
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
[DRAFT] export dataset to Hub UI + Backend testing branch #5725
Closed
Conversation
This file contains 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
…port-dataset-to-hub
…-hub-testing-merge
…o-hub-testing-merge
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5725 +/- ##
===========================================
- Coverage 92.00% 90.68% -1.32%
===========================================
Files 161 161
Lines 6778 6977 +199
===========================================
+ Hits 6236 6327 +91
- Misses 542 650 +108
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…port-to-hub-frontend
…port-dataset-to-hub-testing-merge
…o-hub-testing-merge
…lla-io/argilla into feat/export-to-hub-frontend
# Description This PR adds a new endpoint to support exporting an Argilla dataset to HuggingFace Hub. Being the endpoint `POST /api/v1/datasets/:dataset_id/export` with the following expected body: - `name`: the name of the dataset to be created on HF Hub. i.e. `username/my-new-dataset`. - `subset` (optional, default: `default`): the subset of the dataset to be created. - `split` (optional, default: `train`): the split of the dataset to be created. - `private` (optional, default: `false`): whether the dataset should be private or not. - `token`: the HF Hub API access token to create the dataset, it should have WRITE access. **Type of change** - New feature (non-breaking change which adds functionality) **How Has This Been Tested** - [x] Testing manually exporting some datasets. **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 - I confirm My changes generate no new warnings - I have added tests that prove my fix is effective or that my feature works - I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
…port-dataset-to-hub-testing-merge
…o-hub-testing-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Only a branch that we will use to join UI + Backend changes associated with dataset export to hub.