ci: switch CI to paths-filter so pytest reports on docs-only PRs

[yoshi280]

Unblocks #426 (and any future docs-only PR).

Problem

required_status_checks ruleset on main requires pytest (3.12) and pytest (3.13) to pass. The CI workflow's paths-ignore: ['docs/**', '**/*.md', ...] causes the entire workflow to skip on docs-only PRs, so those checks never report — main rejects the FF push with 2 of 5 required status checks expected.

Caught while attempting to land #426 (README v1.7 row → shipped) as part of the v2.0 reproducibility-cut sequence.

Fix

Per the existing TODO note in .github/workflows/ci.yml: replace the workflow-level paths-ignore with an in-job dorny/paths-filter@v3 step. The job always runs (so the required check always reports a status) but the install + test steps are conditional on code paths having actually changed. Docs-only PRs short-circuit and report a green check.

Test plan

• Self-test: this PR is itself a CI / non-docs change, so it triggers the new pytest invocation. CI must remain green for pytest (3.12) and pytest (3.13).
• Post-merge: re-rebase docs(readme): v1.7 row → shipped (BM25F default-on; others opt-in) per #154 #426 onto new main and verify pytest reports green via the docs-only short-circuit.
• Post-merge: any future docs-only PR sees the same short-circuit pass.

Refs

• TODO note: previous `.github/workflows/ci.yml:9-11` ("migrate to a `dorny/paths-filter` detection job so the workflow always runs and reports a status, with downstream jobs gated by `if:`").
• Originally surfaced under PR merging / review / CI pipeline too strict #413; deferred until branch protection started enforcing the check.
• Blocking: docs(readme): v1.7 row → shipped (BM25F default-on; others opt-in) per #154 #426 ([retrieval] Pipeline composition tracker — unified retrieve() with feature-flag gate #154 task 4 — README v1.7 row → shipped).
• Sister: ci(replay-soak-gate): scope to #264-touching paths only #443 (paths-filter on the soak-gate workflow; orthogonal — that one trims advisory noise, this one unblocks the required-check rule).

Summary by Sourcery

Ensure CI pytest jobs always run and report status while short-circuiting on non-code changes.

CI:

• Replace workflow-level paths-ignore with in-job dorny/paths-filter usage to detect code vs non-code changes.
• Gate environment setup and pytest steps on code path changes so docs-only PRs report a passing required check without running tests.

[sourcery-ai]

Reviewer's Guide

Switches CI from workflow-level paths-ignore to in-job dorny/paths-filter-based gating so that pytest checks always run and report, but installation and tests are skipped for docs-only changes.

Sequence diagram for CI workflow with paths-filter gating pytest

sequenceDiagram
    actor Developer
    participant GitHub
    participant CI_Workflow
    participant PathsFilter as dorny_paths_filter_v3
    participant SetupUV as setup_uv
    participant Pytest as pytest_job

    Developer->>GitHub: Open_or_update_pull_request
    GitHub-->>CI_Workflow: Trigger_CI_on_pull_request_to_main

    CI_Workflow->>PathsFilter: Run_paths_filter_with_code_filters
    PathsFilter-->>CI_Workflow: code_output_true_or_false

    alt Code_paths_changed
        CI_Workflow->>SetupUV: Run_setup_uv_with_python_version
        SetupUV-->>CI_Workflow: Environment_ready
        CI_Workflow->>Pytest: uv_sync_frozen_dev_archive
        Pytest-->>CI_Workflow: Dependencies_installed
        CI_Workflow->>Pytest: uv_run_pytest_tests_ignore_e2e
        Pytest-->>GitHub: Report_required_status_check_pass_or_fail
    else No_code_paths_changed_docs_only
        CI_Workflow->>GitHub: Run_echo_no_code_paths_changed
        CI_Workflow-->>GitHub: Report_required_status_check_pass
    end

Loading

File-Level Changes

Change	Details	Files
Ensure CI workflow always runs while conditionally gating pytest setup and execution on code-path changes using dorny/paths-filter.	Remove pull_request.paths-ignore block that previously skipped the CI workflow entirely for docs-only changes. Add dorny/paths-filter@v3 step to detect changes in code-related paths (src, tests, pyproject.toml, uv.lock, ci workflow). Gate setup-uv, dependency installation, and pytest commands behind an if: steps.filter.outputs.code == 'true' condition. Add final no-op echo step that runs when no code paths changed to mark docs-only PRs as passing while avoiding pytest execution. Update workflow comments to document the new behavior and its relationship to required pytest status checks and referenced issues.	.github/workflows/ci.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@yoshi280 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 53 minutes and 20 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a56fae14-9c07-45d8-93b3-56bfc0c3c386

📥 Commits

Reviewing files that changed from the base of the PR and between a3e4940 and e6f0290.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/paths-filter-always-report-pytest

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}