-
Notifications
You must be signed in to change notification settings - Fork 249
[AgentX]: B300 Kimi K3 DSpark refresh #2476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cquil11
wants to merge
2
commits into
main
Choose a base branch
from
agent/refresh-kimik3-b300-dspark-agentx
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 AGENTS.md (Git conventions, line 82) requires every commit message/PR title to include a Simplified Chinese translation alongside English, since squash-merge inherits the PR title as the commit subject. Both this PR's title ('[AgentX]: B300 Kimi K3 DSpark refresh') and the resulting squash commit are English-only with no 中文 translation. This is a metadata/convention gap, not a functional bug, so it's easily fixed by amending the PR title (or a follow-up commit note) to add the Chinese translation.
Extended reasoning...
What the convention requires:
AGENTS.mdstates under Git conventions: "Commit messages must include a Simplified Chinese translation in addition to English — keep the subject line in English (conventional-commit style), then include the Chinese translation of the subject and key body points in the commit body... Squash-merge commits inherit the bilingual PR title, which satisfies the subject requirement automatically." That last sentence makes the PR title the actual enforcement point for squash-merged PRs like this one, since GitHub squash-merge by default uses the PR title as the resulting commit subject.Where it was violated: The PR title is
[AgentX]: B300 Kimi K3 DSpark refresh— English only, no中文:translation. I confirmed the resulting merged commit withgit log -1 --format=%B 743b761, which returns exactlyperf(agentx): refresh B300 Kimi K3 DSparkwith no body and no Chinese translation at all. Per the AGENTS.md rule, this commit needed either a bilingual PR title (inherited into the subject) or a trailing中文:<translation>paragraph in the body — it has neither.Why nothing else in the repo catches this: There is no CI check enforcing bilingual commit/PR titles (unlike the doc-mirroring rule for
_zh.mdfiles, which is a hard requirement with its own convention but still no automated gate that I could find). Enforcement here is purely reviewer-driven, which is why it slipped through on this PR as well as on the immediately preceding commits (#2420,#2421,#2464) — this appears to be a widely-unenforced convention rather than something unique to this change.Step-by-step proof:
AGENTS.mdline 82 (Git conventions section) states the bilingual requirement and explicitly calls out that squash-merge commits satisfy it via the PR title.[AgentX]: B300 Kimi K3 DSpark refresh— no Chinese text present.git log -1 --format=%B 743b761(the squash-merge commit that added thisperf-changelog.yamlentry) returns a single English line,perf(agentx): refresh B300 Kimi K3 DSpark, with no body and no中文:section.Impact and fix: This causes no functional failure — the changelog entry, config keys, and PR content are all correct, and nothing breaks at merge or runtime. It is a documentation/process compliance gap. The fix is simply to amend the PR title (or add a commit-body note before merge) to include a
中文:<subject translation>line, e.g.中文:刷新 B300 Kimi K3 DSpark 提交. Given the non-functional nature and the fact that recent adjacent commits have the same gap, this should be treated as a nit rather than a blocking issue.