Development record
Hosted CI reuses test results that cannot have changed
Press Release
Hosted CI reuses the Go test results that cannot have changed, as the person's machine does, by restoring file times in a fresh checkout so a test that read an unchanged file is not rerun, cutting the hosted minutes a private repository pays for.
Why This Matters
Why this matters to the user — replace before planning.
Mechanism
Prompted (the claim-recording gradient): why the authors expect this to work, as a falsifiable "we expect X because Y" — not the outcome restated. Replace this line with the claim, or with the exact token
None stated.alone on its line to record the claim as considered and declined.
Scope Conditions
Required (the claim-recording gradient): the population, platform, scale, or assumptions this claim holds under, one per top-level bullet —
abcd intent planstamps each with a persistent identity. Replace this line with those bullets, or with the exact tokenNone stated.alone on its line.
Acceptance Criteria
Required (the itd-1 discipline): add at least one Given-When-Then bullet describing the verifiable bar for "shipped" before this draft can be planned.
Open Questions
None recorded yet.
Audit Notes
Empty. Populated by intent-auditor when intent moves to shipped/.
Frontmatter
| id | itd-2611012123505400 |
|---|---|
| type | intent |
| lifecycle | drafts |
| severity | minor |
.abcd/development/intents/drafts/itd-2611012123505400-hosted-ci-reuses-the-go-test-results.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-1Every Intent Has Acceptance Criteria; Every Audit Verifies Them