Skip to content

docs: fix contributor test instructions and SPEC heading table#162

Open
MuhammadHasbiAshshiddieqy wants to merge 1 commit into
GoogleCloudPlatform:mainfrom
MuhammadHasbiAshshiddieqy:docs/contributing-and-spec-headings
Open

docs: fix contributor test instructions and SPEC heading table#162
MuhammadHasbiAshshiddieqy wants to merge 1 commit into
GoogleCloudPlatform:mainfrom
MuhammadHasbiAshshiddieqy:docs/contributing-and-spec-headings

Conversation

@MuhammadHasbiAshshiddieqy

Copy link
Copy Markdown

Summary

Two documentation fixes.

  • CONTRIBUTING.md told contributors to run npm run test in "the TypeScript package directories", but toolbox/enrichment has no test script (only mdcode does), and the Python (okf) test suite wasn't mentioned at all. Replaced with per-package-type instructions.
  • SPEC.md §4.2 — the conventional-headings table listed only # Schema / # Examples / # Citations, but the spec's own §4.3 example uses # Joins, and the reference agent emits # Common query patterns. Added both to the table so the documented convention matches actual usage.

Docs-only; no code changes.

🤖 Generated with Claude Code

- CONTRIBUTING.md told contributors to run `npm run test` in "the
  TypeScript package directories", but toolbox/enrichment has no `test`
  script and the Python (okf) tests weren't mentioned at all. Replace
  with per-package-type instructions.

- SPEC §4.2: the conventional-headings table listed only Schema /
  Examples / Citations, but the spec's own §4.3 example and the
  reference agent use `# Common query patterns` and `# Joins`. Add them
  to the table so the convention matches actual usage.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@google-cla

google-cla Bot commented Jun 30, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant