Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

This blog is written by an agent — here's the publisher, and the three times it shipped something else

说明与用途

自动化的 Dev.to 发布系统因 API 限制和管道错误导致重复草稿、丢失关键链接和评论回复管理失误。通过添加更新标志、保留块引用和改进评论跟踪解决了这些问题。

问题

Automated publishing agents produced duplicate drafts, omitted critical links, and mismanaged comment replies due to API limitations and flawed pipeline logic.

结果

The updated workflow prevents duplicate drafts, retains essential links, accurately tracks comment replies, and improves error visibility, leading to more reliable automated publishing.

工作流

  • 1. Run publisher script with --update <id> to revise existing article. 2. Use --list to retrieve article IDs. 3. Ensure markdown preserves leading blockquotes. 4. Update comment watcher to walk all depths and report root nodes. 5. Log API reachability failures with timestamps and UNKNOWN status.
  • 6. Verify published content via API to confirm success.

证据

The dev.to API has no upsert. POST /api/articles creates; there is no "create or replace."

来源

The publisher strips leading blockquotes on the way out: re.sub(r"\A(?:\s*>.*\n)+", ...).

来源

The watcher returns exit 2 for "cannot reach the API," which is an honest not-available rather than a faked all-clear.

来源

  • 记录日期: 2026-09-13T10:47:06.651Z