Repository navigation
[PR] docs: point the media-split digest comments at #6356, not the unrelated #6351 (post-merge supplement to #6357) - #6536
ranxianglei wants to merge 1 commit into
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.9567-pr.6536.9e62d7fThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6536.tgz
npm install -g packageInstall instructions are refreshed on each push. |
731eacf to
d7edf18
Compare
(ai: vllm-qwen/qwen3.8-27b) This is a [PR] thread — PR #6536 already exists with the correct diff, so I verified it rather than re-doing the work, and I fixed its one red CI shard. What I verified
CI — the original head (731eacf) had one red shard: Action taken — per §7.2 I rebased the branch onto current master (a007974) and pushed (new head Status — PR #6536 is open, mergeable, now on current master, labels 八问(中文):
判定:可合(等全新 CI 绿)。 |
Post-merge supplement to #6357 (landed via batch #6464 as 47f0b96).
What
The batch cherry-pick landed the fix commit but dropped the follow-up docs commit 828aed7, so the two comments it introduced still cite #6351 — an unrelated open PR (fold before pi's cancelled auto-compaction) — instead of #6356, the bug they describe. A reader following the comment ref lands on the wrong PR.
This restores that exact two-line change, cherry-picked with -x from 828aed7:
Why it matters
Comments only — no code change, no behavior change. Pure reference hygiene so the landed fix points at its own issue.
Verification
Closes nothing — the source issue #6356 is already closed as completed; this only completes the landing of the author's own commit that the batch dropped.