Repository navigation
[PR] fix(ci): post carry receipts with -F so the @- stdin field is parsed - #4519
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5471-pr.4519.a394e1cThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4519.tgz
npm install -g packageInstall instructions are refreshed on each push. |
ranxianglei
force-pushed
the
2026-10-24_carry-receipt-fix
branch
from
October 24, 2026 10:23
692ea79 to
acbfde1
Compare
ranxianglei
force-pushed
the
2026-10-24_carry-receipt-fix
branch
from
October 24, 2026 10:25
acbfde1 to
17ce719
Compare
Contributor
|
(ai: zai/glm-5.3) backport carry: every pick conflicted — nothing clean to push yet. Conflicting picks (resolve manually on a fresh branch off git checkout -b <fix-branch> origin/bugfix-v0.1.206
git cherry-pick -x 17ce7193 # resolve the <<<<<<< markers, then continue
git cherry-pick -x 04558109 # resolve the <<<<<<< markers, then continue
git push origin HEAD:<fix-branch> # open a PR against bugfix-v0.1.206, label it backport-carry |
This was referenced Oct 24, 2026
…nc regenerates clean #4505 added the flag (src/rollout.ts) and hand-wrote its doc rows but never registered it in website/config-reference/rollout.yaml, so every docs-sync run regenerates without the row and fails git diff --exit-code. Adding the seed entry restores idempotency; the generator normalizes the row (no backticks in generated descs, single default cell) and adds the env-map row it had been missing.
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.817-master.0022ae7 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(ai: zai/glm-5.3)
Fixes #4518
这是啥问题?
#4503 合并时打 backport 标签触发的真实首跑(09:55Z)证明新机器人主路径正确(自动切出
bugfix-v0.1.206车道、检测 merge-commit、逐个 pick),但三处回执评论路径全坏:gh api ... -f body=@-里小写-f不解析@-(stdin 语法只在-F/--field生效),于是评论被发成字面字符串"@-"——冲突清单与手动重放命令静默丢失。改动
.github/workflows/backport.yml三处(共 3 行,每行一个字符):-f body=@-→-F body=@-。为什么不是更大改动
gh help api:"if the value starts with@, the rest of the value is interpreted as a filename… Pass-to read from standard input" ——该解析归属-F/--field;管道形态本身({ …; } | gh api …)保持不变。成功路径(#4503 之前从无人走到过)首次生产验证时即暴露本 bug,属回归级缺陷而非设计问题。测试
yaml.safe_load通过;"@-"(comment 6382794648,已删);附带清理(同 commit 前已完成,API)
删除 #4503 上那条
"@-"垃圾评论(id 6382794648)。#4503 的 3 个 pick 在 v0.1.206 车头上全部真实冲突(tag 之后 ci.yml/AGENTS.md/release.md 等被后续 PR 改动);因内容全是.github/+文档(不进 npm 包、bot 从 master 读定义),无需补 carry——下次有人真正走「临时 fix 打标」路径时才会验证成功路径的回执渲染。