Restrict further what changes auto-trigger cloud tests #2778
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
s-urbaniak
reviewed
Oct 8, 2025
s-urbaniak
approved these changes
Oct 8, 2025
Co-authored-by: Sergiusz Urbaniak <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Being more specific should avoid cloud tests run when changing workflows or new autogeneration related code, which is not yet connected in production.
Reminders:
Proof of Work
Need to wait for merging in main to ensure the filtering works as expected.
✅ workflow change did not trigger cloud tests
✅ internal/v3 dummy change and workflow change did NOT trigger cloud tests
Checklist