Skip to content

remove iii prefix from all workers except iii-directory#1969

Open
anthonyiscoding wants to merge 2 commits into
mainfrom
docs/drop-iii-prefix
Open

remove iii prefix from all workers except iii-directory#1969
anthonyiscoding wants to merge 2 commits into
mainfrom
docs/drop-iii-prefix

Conversation

@anthonyiscoding

@anthonyiscoding anthonyiscoding commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

What

Remove iii- prefix from iii workers in the docs (except iii-directory)

Why

We're dropping the prefix and docs need to match

Notes

  • One-shotted successfully w/ iii harness, did better than Claude which missed lots of entries.
  • This is a rename only, the tutorials haven't been tested against it yet.

Summary by CodeRabbit

  • Documentation
    • Updated worker names, trigger types, configuration examples, commands, and links to use the current naming convention.
    • Clarified default worker-manager port behavior for automatically spawned workers.
    • Refreshed tutorials and quickstarts with current setup instructions, including queue-based durable execution and updated Linkly examples.
    • Corrected references to worker-manager access control, observability, queues, streams, HTTP, state, and sandbox workers.

@vercel

vercel Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
iii-website Ready Ready Preview, Comment Jul 15, 2026 8:00pm

Request Review

@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This documentation-only change replaces legacy iii-* worker and trigger identifiers with current names across CLI references, worker guides, configuration examples, API references, and Linkly tutorials. It also clarifies worker-manager listener terminology and the CLI port default.

Changes

Worker naming documentation

Layer / File(s) Summary
Worker registry and setup references
docs/next/cli-reference/*, docs/next/creating-workers/*, docs/next/quickstart.mdx, docs/next/using-iii/*, docs/next/understanding-iii/*
Worker commands, configuration examples, registry dependencies, and worker descriptions use names such as http, state, queue, observability, and sandbox.
worker-manager and RBAC guidance
docs/next/creating-workers/functions.mdx, docs/next/creating-workers/worker-manager.mdx, docs/next/creating-workers/workers.mdx, docs/next/tutorials/linkly/frontend.mdx, docs/next/using-iii/*
Trusted and RBAC-gated listener examples consistently use worker-manager.
Trigger and SDK references
docs/next/creating-workers/triggers.mdx, docs/next/reference/*, docs/next/understanding-iii/index.mdx, docs/next/using-iii/functions.mdx
Trigger links, protocol examples, enqueue documentation, and SDK comments use current trigger and worker identifiers.
Linkly tutorial worker flows
docs/next/tutorials/linkly/*
Linkly setup, persistence, observability, durable execution, frontend, overview, and streaming chapters use the renamed workers and updated durable enqueue example.

Estimated code review effort: 2 (Simple) | ~15 minutes

Possibly related PRs

  • iii-hq/iii#1951: Updates the queues guide in the same documentation area with DLQ and redrive/discard behavior.

Suggested reviewers: guibeira

Poem

A rabbit hops through docs so bright,
Renaming workers left and right.
http, state, and queue now gleam,
worker-manager guards the stream.
Port defaults join the parade—
A tidy trail for builders laid.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly describes the main documentation rename and matches the changeset.
Description check ✅ Passed The description includes the required What, Why, and Notes sections and is sufficiently specific.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/drop-iii-prefix

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

skill-check — docs

32 verified, 662 skipped.

7 warnings across the verified workers.

File Approximate line Severity Violation
docs/next/creating-workers/sandboxes.mdx ~119 warning The doc uses iii worker sandbox upload and iii worker sandbox download, which match the outdated iii worker sandbox <verb> form flagged by the CLI rules as outdated; the replacement form is iii trigger sandbox::<verb> — replace or verify that these upload/download subcommands exist under a valid iii worker sandbox surface, and if the file-copy operation is genuinely a CLI subcommand, confirm it isn't the deprecated sandbox form.
docs/next/creating-workers/sandboxes.mdx ~129 warning iii worker sandbox upload follows the outdated iii worker sandbox <verb> pattern the CLI rules mark as deprecated in favour of iii trigger sandbox::<verb> — flag as outdated with the replacement noted.
docs/next/creating-workers/sandboxes.mdx ~135 warning iii worker sandbox download follows the outdated iii worker sandbox <verb> pattern the CLI rules mark as deprecated in favour of iii trigger sandbox::<verb> — flag as outdated with the replacement noted.
docs/next/understanding-iii/index.mdx ~80 warning [Terminology.Hedges] Weak intensifier/hedge 'actually' adds emphasis, not information. Cut it or state the claim directly. (warning)
docs/next/understanding-iii/index.mdx ~196 warning [Terminology.Hedges] Weak intensifier/hedge 'just' adds emphasis, not information. Cut it or state the claim directly. (warning)
docs/next/understanding-iii/index.mdx ~277 warning [Terminology.Hedges] Weak intensifier/hedge 'just' adds emphasis, not information. Cut it or state the claim directly. (warning)
docs/next/using-iii/console.mdx ~166 warning [Terminology.Hedges] Weak intensifier/hedge 'actually' adds emphasis, not information. Cut it or state the claim directly. (warning)

Caution

32 in-scope rendered artifact(s) are out of date — sources this PR touches changed without re-rendering.

  • docs/next/cli-reference/index.mdx.skill.md
  • docs/next/creating-workers/functions.mdx.skill.md
  • docs/next/creating-workers/http.mdx.skill.md
  • docs/next/creating-workers/observability.mdx.skill.md
  • docs/next/creating-workers/queues.mdx.skill.md
  • docs/next/creating-workers/sandboxes.mdx.skill.md
  • docs/next/creating-workers/triggers.mdx.skill.md
  • docs/next/creating-workers/worker-manager.mdx.skill.md
  • docs/next/creating-workers/worker-manifest.mdx.skill.md
  • docs/next/creating-workers/workers.mdx.skill.md
  • docs/next/how-to/schedule-cron-task.mdx.skill.md
  • docs/next/quickstart.mdx.skill.md
  • …and 20 more (see the workflow logs)
  • Re-render this branch and commit rendered artifacts

Check the box above to trigger a workflow run that re-renders and pushes a commit with the artifacts.
This will add an additional commit on this branch — run git pull to sync your local copy before making further changes.

@mintlify

mintlify Bot commented Jul 15, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
iii 🟢 Ready View Preview Jul 15, 2026, 7:56 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.


```bash
iii worker add iii-worker-manager
iii worker add worker-manager

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one is still iii-worker-manager, this worker will be deleted after DX work, it is being replaced by rbac-proxy

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/next/tutorials/linkly/observability.mdx (1)

43-43: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Format the worker name consistently.

Consider wrapping observability in backticks for formatting consistency, especially since it starts the sentence.

♻️ Proposed formatting
-  **observability emits OpenTelemetry.** Its traces, metrics, and logs are emitted as OTel, so
+  **`observability` emits OpenTelemetry.** Its traces, metrics, and logs are emitted as OTel, so
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/next/tutorials/linkly/observability.mdx` at line 43, Update the opening
observability statement to wrap the worker name “observability” in backticks,
preserving the existing sentence and wording.
docs/next/understanding-iii/index.mdx (1)

142-144: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Format worker names consistently.

For consistency with other references in the documentation, consider wrapping http, cron, and state worker names in backticks.

♻️ Proposed formatting
-trigger types alongside their configuration schemas. The http Worker provides the `http` trigger
-type. The cron Worker provides the `cron` trigger type. The state Worker provides the
+trigger types alongside their configuration schemas. The `http` Worker provides the `http` trigger
+type. The `cron` Worker provides the `cron` trigger type. The `state` Worker provides the
 `state` trigger type. A Trigger of a given type can only be registered while a Worker advertising
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/next/understanding-iii/index.mdx` around lines 142 - 144, Format the
worker names `http`, `cron`, and `state` as inline code in the trigger-type
documentation sentence, while leaving the surrounding wording unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/next/creating-workers/http.mdx`:
- Around line 3-17: Update the historical references in docs/changelog/index.mdx
to replace legacy worker IDs, configuration filenames, and config.yaml entries
with the new bare worker slugs, while preserving iii-directory references
unchanged.

---

Nitpick comments:
In `@docs/next/tutorials/linkly/observability.mdx`:
- Line 43: Update the opening observability statement to wrap the worker name
“observability” in backticks, preserving the existing sentence and wording.

In `@docs/next/understanding-iii/index.mdx`:
- Around line 142-144: Format the worker names `http`, `cron`, and `state` as
inline code in the trigger-type documentation sentence, while leaving the
surrounding wording unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: f5de3f76-2d49-4da0-88d8-0616c4d17cf0

📥 Commits

Reviewing files that changed from the base of the PR and between 382f09a and d694db0.

📒 Files selected for processing (32)
  • docs/next/cli-reference/index.mdx
  • docs/next/creating-workers/functions.mdx
  • docs/next/creating-workers/http.mdx
  • docs/next/creating-workers/observability.mdx
  • docs/next/creating-workers/queues.mdx
  • docs/next/creating-workers/sandboxes.mdx
  • docs/next/creating-workers/triggers.mdx
  • docs/next/creating-workers/worker-manager.mdx
  • docs/next/creating-workers/worker-manifest.mdx
  • docs/next/creating-workers/workers.mdx
  • docs/next/how-to/schedule-cron-task.mdx
  • docs/next/quickstart.mdx
  • docs/next/reference/engine-protocol.mdx
  • docs/next/reference/sdk-browser.mdx
  • docs/next/reference/sdk-node.mdx
  • docs/next/reference/sdk-rust.mdx
  • docs/next/tutorials/linkly/durable-execution.mdx
  • docs/next/tutorials/linkly/foundations.mdx
  • docs/next/tutorials/linkly/frontend.mdx
  • docs/next/tutorials/linkly/observability.mdx
  • docs/next/tutorials/linkly/overview.mdx
  • docs/next/tutorials/linkly/persistence.mdx
  • docs/next/tutorials/linkly/streaming.mdx
  • docs/next/understanding-iii/engine.mdx
  • docs/next/understanding-iii/index.mdx
  • docs/next/using-iii/configuration.mdx
  • docs/next/using-iii/console.mdx
  • docs/next/using-iii/engine.mdx
  • docs/next/using-iii/functions.mdx
  • docs/next/using-iii/triggers.mdx
  • docs/next/using-iii/workers-registry.mdx
  • docs/next/using-iii/workers.mdx

Comment on lines +3 to +17
description: "Expose functions as HTTP endpoints with the http worker."
owner: "devrel"
type: "how-to"
---

The `iii-http` worker exposes your functions as HTTP endpoints, turning a function into a REST route
The `http` worker exposes your functions as HTTP endpoints, turning a function into a REST route
without standing up a separate web server.

```bash
iii worker add iii-http
iii worker add http
```

<Note>
This page is a quick tour. For path patterns, methods, headers, and response handling, see the
[iii-http worker docs](https://workers.iii.dev/workers/iii-http). The worker's server settings
[http worker docs](https://workers.iii.dev/workers/http). The worker's server settings

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update the historical changelog references for this rename.

The worker rename also requires docs/changelog/index.mdx to replace legacy worker IDs, config filenames, and config.yaml entries with the new bare slugs (while preserving iii-directory). Otherwise the documentation set remains inconsistent.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/next/creating-workers/http.mdx` around lines 3 - 17, Update the
historical references in docs/changelog/index.mdx to replace legacy worker IDs,
configuration filenames, and config.yaml entries with the new bare worker slugs,
while preserving iii-directory references unchanged.

Source: Path instructions

@guibeira

Copy link
Copy Markdown
Contributor

Hey @anthonyiscoding we only migrated the http, cron, queue, state e pubsub, the rest still as builtin.

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.

3 participants