Skip to content

Restrict further what changes auto-trigger cloud tests #2778

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
josvazg merged 4 commits into from
Oct 8, 2025
Merged

Restrict further what changes auto-trigger cloud tests #2778

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c9ef39e
Restrict what changes auto trigger cloud tests
josvazg Oct 8, 2025
fb1169b
Dummy change in internal/v3 should not trigger cloud tests
josvazg Oct 8, 2025
6c6ae7d
Revert "Dummy change in internal/v3 should not trigger cloud tests"
josvazg Oct 8, 2025
d6d2d33
fix typo
josvazg Oct 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions .github/workflows/cloud-tests-filter.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,15 +26,13 @@ jobs:
# production code also includes changes to e2e and int tests,
# note any other paths are covered by unit testing which run always
# internal/v3 code for feature generation should not trigger old cloud tests
# .github changes should not trigger cloud tests by default
filters: |
production-code-changed:
- 'cmd/**/!(*_test.go)'
- 'pkg/**/!(*_test.go)'
- 'internal/**/!(*_test.go)'
- 'internal/controller/**/!(*_test.go)'
- 'Dockerfile'
- 'test/e2e/**'
- 'test/int/**'
- '!internal/v3/**'
# run only if 'production-code' files were changed
- name: Production code changed
if: steps.paths-filter.outputs.production-code-changed == 'true'
Expand Down
Loading