Repository navigation
ci: auto-trigger codex e2e on request-pipeline PRs (#1296 note-4 hardening) - #1297
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-1297Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr1297.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
[bot] 🏷 收到,开始 review。这是 [PR] issue,我按 PR 审查流程走(原 issue 方向 → 回归 → 代码 → diff 整洁),不重做实现。已拉取分支( |
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.
Hardens the optional step ④ noted in #1296 (v0.1.148 release PR body): #1284/#1290 both moved
src/server.tsrouting, but the e2e suite only ran when someone remembered to dispatch it manually. This makes the memory structural.What changes
ci-e2e.ymlgains apull_requesttrigger (master-targeting, path-filtered) on the request-pipeline hot files —src/server.ts,src/server/**,src/loop/**,src/compress-loop*.ts,src/stream*.ts,src/persist.ts,src/agent/**,tests/e2e/**,package-lock.json(an acp-kernel pin bump IS a pipeline change — it's bundled inline), and the workflow itself.workflow_dispatchstays for everything else.Cost/correctness guards
e2e-${{ github.ref }}withcancel-in-progress— the suite spends real upstream tokens; a fresh push cancels the superseded run, never two in parallel.::notice::+E2E_SKIPenv gate on every downstream step — green skip, not a red failure. Maintainer dispatches manually for fork contributions.ACP_TEST_E2Edefault-skip gate and the pinned codex 0.147.0 ([e2e] fake-upstream overflow 测试与仓库 AGENTS.md 体积隐性耦合:AGENTS.md 增长即破坏 CI(#803 触发) #815) are untouched.Docs
AGENTS.md§E2E: "manual-dispatch only" → auto-trigger description (paths + skip semantics).tests/e2e/README.mdCI section: same, and fixes the stale claim that forge comes from a repository variable (it's the dispatch input feeding theE2E_FORGEenv).Validation
workflow_dispatch,pull_request.ci-e2e.ymlmatches its own path filter — it does, so this PR self-tests the trigger (expect one e2e run using repo secrets; forge off).Refs: #1296 (note ④), #1284, #1290, #1289.