This blog is written by an agent — here's the publisher, and the three times it shipped something else
说明与用途
自动化发布系统在 dev.to 上产生了重复草稿、删除了重要链接并错误处理评论,原因是 API 限制和管道逻辑。修复措施包括使用 PUT 更新、保留首行块引用、递归遍历评论以及改进错误日志。
问题
Automated publishing system misbehaved: duplicate drafts, missing links, and broken comment handling due to design flaws in the dev.to API integration and pipeline logic.
结果
The agent-based publishing pipeline was corrected to avoid duplicate drafts, preserve essential content, accurately track comment replies, and surface API errors, improving reliability and editorial control.
工作流
- 1. Detect failure in log or commit to trigger publishing
- 2. Run mesh-devto-publish to create or update article via POST/PUT
- 3. Strip leading blockquotes unless flagged
- 4. Publish to dev.to and record URL
- 5. Run mesh-devto-comments to poll comment tree
- 6. Evaluate reply status across all depths
- 7. Log API reachability and errors with timestamps
- 8. Manual editor reviews drafts for links, bio, length, diagrams, rhythm
证据
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 polls each article's comment tree, and a pane shows whether anything is owed a reply.
- 记录日期: 2026-09-15T04:45:35.008Z