Skip the CI work you already did.
If nothing a CI step depends on has changed, Quod reuses its last result instead of running it again. Your checks finish in seconds, not minutes.
- Set up job3.1s
- Checkout2.4s
- Set up Go14.0s
- Download modules9.6s
- Build21.4s
- go test ./...17.0s
How it works
- 1
Watch
Quod runs your CI step and notes every file it reads.
- 2
Compare
On your next push, it checks whether any of those files changed.
- 3
Reuse
Nothing changed? You get the last result in under a second. Something changed? The step runs as usual.
Try it
Change a file, run the tests, and see what Quod reuses.
Every skip shows its proof.
You always see which run a result came from and which files matched.
Reused, not run. Quod skipped the step and gave you the result of an earlier run.
Safe by default.
- It starts by only watching. Nothing is skipped until you turn it on.
- A result is reused only after the step has produced it twice.
- It keeps re-running a few skipped steps to make sure.
Quod starts by only watching.
instead of 17s for a test step that didn’t need to run
wrong skips when we changed each of 29,879 files one at a time
languages tested end to end: Go, Node and Python
One line to set up.
Point your GitHub Actions job at Quod. Everything else stays the same.
Questions
Is this just caching?
A cache saves files you pick. Quod skips whole steps, like your test run, and it decides by looking at every file the step actually read. You don't configure anything.
What if it reuses a result it shouldn't?
It only reuses a result when every file the step read is exactly the same. Steps that use the network are never reused, and Quod keeps re-running a few reused steps to double-check.
Which languages?
Go, Node and Python today. Quod watches files, not code, so more are coming.
Where does it run?
On your own Linux machines, with your existing GitHub Actions workflows.
Push. Prove. Done.
We’re letting teams in a few at a time. Join the waitlist.