Skip to content

Only run trampoline checks in CI when trampolines change#17386

Merged
zanieb merged 2 commits intoastral-sh:mainfrom
zaniebot:claude/conditional-trampoline-checks-JzRFa
Jan 12, 2026
Merged

Only run trampoline checks in CI when trampolines change#17386
zanieb merged 2 commits intoastral-sh:mainfrom
zaniebot:claude/conditional-trampoline-checks-JzRFa

Conversation

@zanieb
Copy link
Member

@zanieb zanieb commented Jan 9, 2026

I'm trying to avoid wasting CI time.

Add a new `trampoline` output to the `determine_changes` job that
detects changes in `crates/uv-trampoline/` or `crates/uv-trampoline-builder/`.
Update both `windows-trampoline-check` and `windows-trampoline-test` jobs
to only run when trampoline-related files are modified (or on main branch),
instead of running on every code change.

This avoids unnecessary Windows CI runs when non-trampoline code changes.
@zanieb zanieb added the internal A refactor or improvement that is not user-facing label Jan 9, 2026
The conditional break saved at most ~100ms per CI run, which isn't
worth the added complexity. Simplify by always iterating through
all changed files.
@zanieb zanieb marked this pull request as ready for review January 9, 2026 23:15
@zanieb zanieb merged commit 0da6f26 into astral-sh:main Jan 12, 2026
102 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal A refactor or improvement that is not user-facing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants