release: publish dataset card (README.md) to HF Hub (RFC-0015 Step 13)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- huggingface, python
- Domain
- data, documentation, release
Research direction
Start by checking that data/DATASET_CARD.md exists and that D1 and D5 are complete. Run the provided huggingface_hub upload_file command with HF_TOKEN for the dataset repository, then inspect the rendered README.md on the Hugging Face dataset page. Done means the YAML front matter, usage snippet, tables, and citation block render correctly.
Written by the indexing model from the issue text.
Description
Context
The dataset card (data/DATASET_CARD.md, created in D1) must be uploaded as README.md to the HF dataset repo. This is what renders in the HF dataset viewer and is the primary discoverability surface.
Command
from huggingface_hub import HfApi
api = HfApi()
api.upload_file(
path_or_fileobj="data/DATASET_CARD.md",
path_in_repo="README.md",
repo_id="CodingJEPA/human-python-refactors",
repo_type="dataset",
token=HF_TOKEN,
commit_message="data: publish dataset card v1.0.0",
)
Acceptance criteria
-
README.mdvisible onhuggingface.co/datasets/CodingJEPA/human-python-refactors. - YAML front-matter renders correctly (HF shows license badge, language tag, config selector).
- Usage snippet (
load_dataset(...)) is copy-pasteable and correct. - Source repos table and intent taxonomy table render without Markdown errors.
- Citation bibtex block is present.
Dependencies
- Requires: D1 (DATASET_CARD.md written), D5 (LICENSES uploaded — card references them)
- Blocks: D7 (smoke test)
RFC references
- RFC-0015 §Step 13, §D1
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbdelStark/CodingJEPA
-
area:release effort:s priority:p1 spec:rfc-0009 spec:rfc-0015 type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AbdelStark/CodingJEPA#197 ·
-
area:release effort:s priority:p1 spec:rfc-0014 spec:rfc-0015 type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AbdelStark/CodingJEPA#194 ·
-
area:release effort:s priority:p0 spec:rfc-0015 type:feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
AbdelStark/CodingJEPA#196 ·
-
area:release effort:m priority:p1 spec:rfc-0015 type:feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
AbdelStark/CodingJEPA#193 ·
-
area:release effort:m priority:p1 spec:rfc-0014 spec:rfc-0015 type:feature
Difficulty 3/5 1-2 days Newbie friendliness 65/100
AbdelStark/CodingJEPA#192 ·
All issues in AbdelStark/CodingJEPA
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100