Repository navigation
codeSplitters checks: edits to an open branch after a push aren't checked, and old runs still count #489
Closed as not planned
Description
Follow-up to #465.
Checks start when a branch is pushed upstream, pulled from upstream, or someone presses Run. Line edits on an open branch don't start any, and the merge gate (refChecks in apps/codesplitters/src/checks.ts) reads the runs on the branch's latest checked sha, so a branch edited after its checks passed still merges on those older results.
Wanted: a branch knows when it last changed (e.g. its newest op time), and a run older than that counts as stale, so the gate waits again. An edit could also queue a debounced run when checks run here.
Activity
QuinnsCode commentedon Oct 11, 2026
what is the current system? remember based on environment we have access to rust wasm in client or if rusty buns bun server rust on server for fast systems level syncing when not on cloudflare system!
QuinnsCode commentedon Oct 11, 2026
Folded into #737, which bundles it with related work for one agent. The details here still apply.
🤖 Generated with Claude Code
codeSplitters checks: what runs here, stale runs after branch edits, …