GeezerVison

No actionable comments were generated in the recent review.

Walkthrough

The README adds a TTDU community example. It lists receipt-photo PDF creation, Korean payroll checking, personal-data redaction, and HWP/HWPX conversion. It states that the offline runner must run on the worker machine. It distinguishes path mode, inline mode, and the TTDU hub API by how they handle files and results.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: Minimal · up to 29d1f

This is a documentation-only addition to the community examples list. The earlier concerns about privacy wording and hub support have been addressed, and no merge-blocking risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly describes the main change: adding TTDU document flows to the community examples.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: e5e6c796-555c-457f-ad54-7e12d16ca5fe

Commits

Reviewing files that changed from the base of the PR and between 4c6496c and 29d1f3d.

Files selected for processing: 1

• README.md

Files skipped from review as they are similar to previous changes: 1

• README.md

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

Thanks, both points were right. I changed the code, not just the wording: the tasks now have a path mode (payload { flow, paths, outDir }) in which the worker reads the files from disk, sends them only to the TTDU runner on 127.0.0.1 and returns only names, sizes and SHA-256, so no file contents go into Trigger.dev payloads or outputs. Inline (base64) mode is documented as self-hosted-only. The README entry now says these flows need the local runner and that the hub runs only server-capable flows and uploads files.