Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ A dataset exists because a question needed it. Do not add datasets, parameters,

## Commits and pull requests

A commit message is one sentence stating the behavior. A dataset arrives as a pull request whose record is committed with it. Merge with a merge commit (`gh pr merge --merge`), then pull `main` and run `scripts/promote <name> <version>` with your own `HF_TOKEN`, in `datascience`: CI holds no Hub token.
A commit message is one sentence stating the behavior. A dataset arrives as a pull request whose record is committed with it. Squash-merge it (`gh pr merge --squash`; merge commits stay allowed for the rare case that needs one), then pull `main` and run `scripts/promote <name> <version>` with your own `HF_TOKEN`, in `datascience`: CI holds no Hub token.

<!-- codebox:board:start -->
## Board
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ Any change under `datasets/<name>/` bumps `metadata.version`, prose included, ex

1. Push your branch and open the pull request, the record committed in it.
2. `check` runs: the dataset's rules, an unpublished version, each tool in the toolshed at its version, and a record of a passing test whose files the Hub holds exactly.
3. Someone other than you reviews it, a critic agent included: does the skill describe the files the record lists and state the recipe's inputs; does the record show the test passed where the build ran; is the version new; are the tools the ones the record shows. They merge with a merge commit (`gh pr merge --merge`).
3. Someone other than you reviews it, a critic agent included: does the skill describe the files the record lists and state the recipe's inputs; does the record show the test passed where the build ran; is the version new; are the tools the ones the record shows. They squash-merge it (`gh pr merge --squash`).
4. Whoever merged promotes it: pull `main`, then, from the clone's root,

```bash
Expand Down