Switch team upload flow to pull requests
Browse files
README.md
CHANGED
|
@@ -32,18 +32,20 @@ hf download YY222/bench --repo-type dataset --local-dir test_data
|
|
| 32 |
python3 scripts/asset/download_assets.py
|
| 33 |
```
|
| 34 |
|
| 35 |
-
## Upload (team
|
| 36 |
|
| 37 |
-
|
| 38 |
-
|
|
|
|
| 39 |
|
| 40 |
```bash
|
| 41 |
python3 scripts/asset/upload_assets.py --dry-run # what would be uploaded
|
| 42 |
-
python3 scripts/asset/upload_assets.py --games G011,G013 #
|
| 43 |
```
|
| 44 |
|
| 45 |
Only games containing real artifacts are uploaded (skeleton-only games are skipped),
|
| 46 |
-
and uploads on disjoint games are safe to run concurrently.
|
|
|
|
| 47 |
|
| 48 |
## Notes
|
| 49 |
|
|
|
|
| 32 |
python3 scripts/asset/download_assets.py
|
| 33 |
```
|
| 34 |
|
| 35 |
+
## Upload (team, via pull requests)
|
| 36 |
|
| 37 |
+
The dataset is read-only for the team: members run the upload script from the bench
|
| 38 |
+
repo, it opens a pull request, and the owner merges it. Any logged-in HF account
|
| 39 |
+
works (`hf auth login` with the member's own token) — no special access needed:
|
| 40 |
|
| 41 |
```bash
|
| 42 |
python3 scripts/asset/upload_assets.py --dry-run # what would be uploaded
|
| 43 |
+
python3 scripts/asset/upload_assets.py --games G011,G013 # open a PR for specific games
|
| 44 |
```
|
| 45 |
|
| 46 |
Only games containing real artifacts are uploaded (skeleton-only games are skipped),
|
| 47 |
+
and uploads on disjoint games are safe to run concurrently. Direct pushes to main
|
| 48 |
+
are owner-only.
|
| 49 |
|
| 50 |
## Notes
|
| 51 |
|