Skip to content

errors: Document publishing to the docs site - #354

Merged
lmars merged 1 commit into
mainfrom
error-workflow
Jul 27, 2026
Merged

errors: Document publishing to the docs site#354
lmars merged 1 commit into
mainfrom
error-workflow

Conversation

@lmars

@lmars lmars commented Jul 25, 2026

Copy link
Copy Markdown
Member

Summary

Records the downstream publish step for error-code changes in errors/README.md and errors/CLAUDE.md.

Edits to this registry are not live on ably.com/docs until they are pulled into the docs site, which vendors this directory as a git submodule. That step is easy to forget after a registry change merges, so it's now written down.

What's documented

After a registry change merges to main, a follow-up PR against ably/docs:

  1. Bumps the ably-common submodule (usually to main).
  2. Runs yarn generate:errors.
  3. Commits the regenerated src/pages/docs/platform/errors/codes/ pages alongside the bump.

The ably/docs check-error-docs CI regenerates and diffs, so out-of-sync pages fail the build. ably/docs#3496 is linked as a worked example.

  • README.md — full step-by-step under a new "Publishing to the docs site" section.
  • CLAUDE.md — condensed version for agents, linking back to the README.

Docs-only change; no code, registry entries, or errors.json touched.

🤖 Generated with Claude Code

Registry edits are not live on ably.com/docs until pulled into the docs
site, which vendors this directory as a git submodule. Record the
downstream step — bump the ably-common submodule in ably/docs, run
`yarn generate:errors`, commit the regenerated pages, open a docs PR —
in README.md and CLAUDE.md so it isn't missed after a registry change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lmars
lmars requested a review from m-hulbert July 25, 2026 12:25
@lmars
lmars merged commit d81ba14 into main Jul 27, 2026
2 checks passed
@lmars
lmars deleted the error-workflow branch July 27, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants