feat: add README publishing workflow - #4
Open
YOIMIYA66 wants to merge 3 commits into
Open
Conversation
YOIMIYA66
marked this pull request as ready for review
May 20, 2026 04:17
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
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.
Summary
Adds a concrete README publishing workflow for AI Studio training runs.
SKILL.mdtrain.pycommands to generate dataset/model README files and push README.md to AI Studio Git repositoriesWhy
In the ERNIE medical-record SFT run, training artifacts were preserved but dataset/model README publishing did not happen automatically. The skill mentioned model cards in prose, but there was no script command for agents or notebooks to call, and dataset README publishing was not part of the upload gate.
Validation
python -m py_compile scripts\train.pypython scripts\train.py --helppython scripts\train.py --generate-dataset-readme <sample.jsonl> --train-data user/demo_dataset --train-file train.jsonl --out <temp README>git diff --check(only existing LF/CRLF warnings on Windows)