Skip to content

ci: auto-trigger codex e2e on request-pipeline PRs (#1296 note-4 hardening) - #1297

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-25_e2e-auto-trigger
Sep 25, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-25_e2e-auto-trigger

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Hardens the optional step ④ noted in #1296 (v0.1.148 release PR body): #1284/#1290 both moved src/server.ts routing, but the e2e suite only ran when someone remembered to dispatch it manually. This makes the memory structural.

What changes

ci-e2e.yml gains a pull_request trigger (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_dispatch stays for everything else.

Cost/correctness guards

  • Concurrency: e2e-${{ github.ref }} with cancel-in-progress — the suite spends real upstream tokens; a fresh push cancels the superseded run, never two in parallel.
  • Secrets gate: secrets are injected only for same-repo PRs and manual dispatch. Fork PRs (no secret access) skip the run gracefully via a ::notice:: + E2E_SKIP env gate on every downstream step — green skip, not a red failure. Maintainer dispatches manually for fork contributions.
  • The ACP_TEST_E2E default-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.md CI section: same, and fixes the stale claim that forge comes from a repository variable (it's the dispatch input feeding the E2E_FORGE env).

Validation

  • YAML parses; trigger keys = workflow_dispatch, pull_request.
  • No workflow run is triggered by this PR itself unless ci-e2e.yml matches 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.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-25_e2e-auto-trigger (95a866b)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1297

Each push to this PR publishes a new version under the pr-1297 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr1297.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 收到,开始 review。这是 [PR] issue,我按 PR 审查流程走(原 issue 方向 → 回归 → 代码 → diff 整洁),不重做实现。已拉取分支(95a866bd),diff 共 3 个文件:ci-e2e.yml(+46)、AGENTS.md、tests/e2e/README.md。注意到 PR base 落后当前 master 5 个 commit(v0.1.148 release 已合入),会一并核对 rebase 干净度与 CI 状态,结论稍后补上。

@ranxianglei
ranxianglei merged commit 22460c6 into master Sep 25, 2026
10 checks passed
ranxianglei pushed a commit that referenced this pull request Sep 25, 2026
…stry + native-lane + #1297 CI wording), lock regen (verdaccio subtree only)
@ranxianglei
ranxianglei deleted the 2026-09-25_e2e-auto-trigger branch October 15, 2026 05:32
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.

1 participant