Skip to content
← Trylle Journal
CIMerge queue

Running CI closer to the merge decision

Checks are only useful when their result is still true at merge time. How we schedule, cache, and re-run work near the tip of a branch.

Alan · Co-Founder1 min read

A green check from four hours and eleven upstream commits ago is a guess, not a guarantee.

Schedule against the merge result

Trylle runs the decisive checks against the commit that would actually exist after the merge, not the branch tip in isolation. Conflicts and semantic breakages surface before the merge button rather than after it.

Reuse what has not changed

Job-level caching is keyed on the inputs a job actually reads. If a branch only touched documentation, the test matrix reuses its previous result instead of burning ten minutes proving nothing changed.