main

文件	最后提交记录	最后更新时间
ci.yml	perf(e2e): run the fork-safe E2E suite in three parallel shards (-52% E2E wall time) (#1237) * test(e2e): stop OpenCode's file watcher in the session migrate test Each OpenCode run subscribed a watcher on every directory above its workspace. In a crowded temp directory that took 10-20 s a run, so the one synchronous test took close to a minute, near Vitest's 60 s worker RPC limit. * ci(e2e): run the fork-safe E2E suite in two parallel shards Each shard keeps 4 workers on its own runner; the files split by vitest's hash into halves of about the same running time. A confirm job keeps the check name branch protection requires and fails unless both shards passed. * ci(e2e): split the fork-safe E2E suite in three shards With CI's per-file times, vitest's hash splits the files 1241/1625 s in two shards and 895/1001/970 s in three. The thinner, even shards also leave room for a slow runner.	14 小时前
code-erosion.yml	docs: reorganize documentation (#1009) - Add docs/README.md index by audience; move CI maintainer notes to docs/dev/; give every design document a status line and index row - Open Getting Started with three ten-minute paths (set up, join, share) - Split the usage guide into pages: docs/guide/<page>.md (English) and docs/guide/zh-CN/<page>.md (Chinese); usage-guide.* stay as index pages - Fold providers (new English translation) and Windows pages into the guide; move provider internals to docs/dev/adding-a-provider.md - Make docs/designs/ and docs/dev/ English only; translate the Chinese-only pages - Replace copied command and flag tables with links to --help and the generated commands.md; drop the stale Windows workaround - Align agent, hook, picker and path claims with the code - Plainer wording across guide pages, index pages and READMEs - Record the doc layout and link-to-help rule in AGENTS.md Claude-Session: https://claude.ai/code/session_01LjCjoz1mXZG1dR7p1iuVr7 Co-authored-by: Claude <noreply@anthropic.com>	12 天前
codex-review-on-assign.yml	chore(review): scope e2e to behavior changes, drop provider×agent matrix, add P3 (#781) * chore(review): scope e2e requirement, drop provider×agent matrix, add P3 The auto-review gate over-flagged: it required a full provider × agent e2e matrix as [P1 blocking] on every PR, raised theoretical/low-confidence risks at blocking severity, and repeated already-resolved findings. - e2e record is [P1 blocking] only for behavior-changing PRs; docs-only / tests-only diffs need none. One representative real-CLI run is enough; missing extra provider/agent coverage the author flagged as untestable here or deferred to CI is at most [P3 nit], never blocking. - Add a third severity [P3 nit] (minor/optional polish, theoretical edge case, coverage deferred to CI). - Tell the reviewer not to over-review: report only high-confidence findings, prefer few high-signal over exhaustive, never restate a resolved finding. Kept in sync across AGENTS.md (## Code Review Rules, the trusted base criteria) and the workflow prompt in codex-review-on-assign.yml. * chore(review): relax PR 前测试 matrix, gate P1 by evidence not count Address SaulMoro's changes-requested on #781: - The provider × agent matrix requirement still lived in `## PR 前测试` (AGENTS.md/CLAUDE.md), which the Codex reviewer loads whole — so the matrix could return as a P1 despite `## Code Review Rules` relaxing it. Relax `## PR 前测试` to match: one representative real-CLI run suffices, docs/tests-only needs no e2e, extra provider/agent coverage defers to CI. - Replace "prefer a few high-signal findings" (which caps real bugs and pushes them to later passes) with evidence-gated severity: every [P1 blocking] must cite a concrete failure scenario or the exact rule it breaks, else it drops to P2/P3. Count is uncapped; real bugs surface in one pass. Synced into the workflow prompt. --------- Co-authored-by: review <review@local>	27 天前
release.yml	fix(ci): pick an explicit release-notes base on the same lineage (#512) GitHub's automatic base selection takes the newest tag reachable from the tagged commit. Release commits are created detached and never land on a branch, so no release tag is an ancestor of the next one and every recent release compared back to v0.22.0 — the last release that happened to be merged into main. The 0.23.x stables are worse: they were cut from an internal mirror sync, so their merge-base with main sits at v0.17.4 and their notes span three months of unrelated PRs. Resolve the base explicitly and feed it to the generate-notes API. A prerelease compares against the tag before it; a stable release compares against the previous stable tag. Both skip tags whose parent is absent from this release's history, so a mirror-sync tag can no longer poison the range. Co-authored-by: Cursor <cursoragent@cursor.com>	1 个月前