Skip to content

docs(rfc-0045): one fix PR per vendor, one commit per difference - #348

Merged
eric8810 merged 1 commit into
masterfrom
claude/project-thread-15ah47
Oct 25, 2026
Merged

eric8810 merged 1 commit into
masterfrom
claude/project-thread-15ah47

Conversation

@cunninghamcard-bit

Copy link
Copy Markdown
Contributor

Summary

改动前:RFC-0045 §5.4 第 4 条要求迁测试时发现的每处行为差异单独开一个 fix PR,Open Responses 一家就开了 16 个。

改动后:同一厂商的差异放进一个 fix PR,一处差异一个提交,每个提交带一个在 master 上失败的测试,描述里每处各写现状和改动两段调用栈;测试 PR 叠在这个 fix PR 上。其余不变(不在测试 PR 里修、登记到偏差清单、刻意差异记进 registered)。

已经开的 fix PR 已按这条合并:Hugging Face #307、xAI #311、Anthropic AWS #318、OpenAI #323、Open Responses #346,其余的已关闭并在评论里指向保留的 PR;进度见 #278。

一、体系概览:迁测试时差异怎么处理(RFC-0045 §5.4)

迁一个厂商的上游测试
├─ 测试通过                         → 测试 PR(src/<vendor>/tests/,layout.toml)
├─ 刻意差异                         → 对齐文档 §5 + layout.toml registered
└─ 行为差异                         → fix PR(本 PR 改的就是这一条)
     └─ 测试 PR 叠在 fix PR 上

二、本 PR 的改动

rfc/0045-upstream-test-parity.md:174   §5.4 第 4 条
  每处差异单独开一个 fix PR  →  同一厂商一个 fix PR,一处一个提交

Type of change

  • Bug fix (non-breaking)
  • New feature (non-breaking)
  • Breaking change
  • New provider
  • New / updated binding
  • Docs / RFC

Checklist

  • Commit messages follow Conventional Commits
  • 只改 RFC 文本一行,不涉及代码

Generated by Claude Code

The behaviour differences found while porting a vendor's upstream tests
go into a single fix PR for that vendor, each difference in its own
commit with a test that fails on master, instead of one PR each.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RoxcKU4zBD64Lri3e4Lrq5
@cunninghamcard-bit
cunninghamcard-bit marked this pull request as ready for review October 24, 2026 11:34

@eric8810 eric8810 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.

RFC-0045 的一行修改与当前批次一致,无阻塞。Approve。

@eric8810
eric8810 merged commit 97f0d84 into master Oct 25, 2026
14 checks passed
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.

2 participants