Skip to content

bug: Run operator tests only when operator files change - #6800

Open
Patrick-SCH03 wants to merge 2 commits into
feast-dev:masterfrom
Patrick-SCH03:ci/operator-pr-paths-filter
Open

bug: Run operator tests only when operator files change#6800
Patrick-SCH03 wants to merge 2 commits into
feast-dev:masterfrom
Patrick-SCH03:ci/operator-pr-paths-filter

Conversation

@Patrick-SCH03

Copy link
Copy Markdown

What this PR does / why we need it:

Part of #6502 (Track 1: low-risk CI hygiene).

operator_pr.yml currently runs on every PR (on: [pull_request]), so even docs-only or Python-only changes install Go and run the full operator test + bundle sync check. This PR adds a paths filter so the workflow only runs when infra/feast-operator/** (or the workflow file itself) changes — mirroring the existing filter in operator-e2e-integration-tests.yml.

Which issue(s) this PR fixes:

Part of #6502 — intentionally not using Fixes, since that issue tracks multiple cleanup items and should stay open.

Checks

  • I've made sure the tests are passing.
  • My commits are signed off (git commit -s)
  • My PR title follows conventional commits format

Testing Strategy

  • Unit tests
  • Integration tests
  • Manual tests
  • Testing is not required for this change

Misc

Since .github/workflows/operator_pr.yml is included in its own paths filter, the operator tests still run on this PR itself, which verifies the workflow remains valid after the change.

Note for maintainers: if operator-test is a required status check in branch protection, path-filtered skips will leave it pending on unrelated PRs. In that case it may need to be removed from required checks, or I can add a no-op fallback workflow with the same job name — happy to do either.

Signed-off-by: Patrick-SCH03 <wwoo5241@gmail.com>
@haoxu0 haoxu0 changed the title ci: run operator tests only when operator files change ci: Run operator tests only when operator files change Aug 30, 2026
@haoxu0 haoxu0 changed the title ci: Run operator tests only when operator files change bug: Run operator tests only when operator files change Aug 30, 2026
@codecov-commenter

codecov-commenter commented Aug 30, 2026

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.09%. Comparing base (5ad5592) to head (f37e794).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #6800   +/-   ##
=======================================
  Coverage   47.08%   47.09%           
=======================================
  Files         419      419           
  Lines       51878    51878           
  Branches     7525     7525           
=======================================
+ Hits        24429    24430    +1     
  Misses      25700    25700           
+ Partials     1749     1748    -1     
Flag Coverage Δ
go-feature-server 30.58% <ø> (ø)
python-unit 48.40% <ø> (+<0.01%) ⬆️
see 1 file with indirect coverage changes

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5ad5592...f37e794. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Signed-off-by: Patrick-SCH03 <wwoo5241@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants