Skip to content

ci: run only PR-affected pytest tests - #203

Closed
plfavreau wants to merge 2 commits into
mainfrom
feat/ci-affected-tests
Closed

ci: run only PR-affected pytest tests#203
plfavreau wants to merge 2 commits into
mainfrom
feat/ci-affected-tests

Conversation

@plfavreau

Copy link
Copy Markdown
Collaborator

What

Make the Feature Integration 🧩 / test check run only the pytest tests affected by the PR diff instead of the full suite, via the shared affected-pytest composite action (minitap-ai/devops-common/.github/actions/affected-pytest@v5).

How

  • Pull requests run pytest --impacted (pytest-impacted: git-diff + AST import-graph) — only tests reachable from changed modules.
  • Push to main still runs the full suite (safety net for anything diff-selection can miss).
  • Force-runs everything when uv.lock / pyproject.toml / a conftest.py change.
  • Added pytest-impacted to dev deps (locked in uv.lock).
  • Added missing __init__.py files so pytest-impacto's pkgutil-based module discovery can see all source subpackages (namespace-package dirs were invisible → false negatives without this).

Depends on devops-common affected-pytest@v5 (already merged + tagged).

Replace the full 'uv run pytest' step with the shared
minitap-ai/devops-common affected-pytest@v5 action (pytest-impacted),
so PRs run only the tests their changed lines impact. Full suite still
runs on push to main. Add pytest-impacted dev dep and the missing
package __init__.py files so namespace dirs are discoverable by the
import-graph analysis (15 new __init__.py).
@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@plfavreau, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 19 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 72594cfa-5126-4a0c-8cfb-6dc61e0fa3c7

📥 Commits

Reviewing files that changed from the base of the PR and between 887fcec and ef1f829.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (17)
  • .github/workflows/feature.yml
  • minitap/mobile_use/agents/contextor/__init__.py
  • minitap/mobile_use/agents/cortex/__init__.py
  • minitap/mobile_use/agents/executor/__init__.py
  • minitap/mobile_use/agents/hopper/__init__.py
  • minitap/mobile_use/agents/orchestrator/__init__.py
  • minitap/mobile_use/agents/outputter/__init__.py
  • minitap/mobile_use/agents/planner/__init__.py
  • minitap/mobile_use/agents/summarizer/__init__.py
  • minitap/mobile_use/clients/__init__.py
  • minitap/mobile_use/graph/__init__.py
  • minitap/mobile_use/sdk/services/__init__.py
  • minitap/mobile_use/services/__init__.py
  • minitap/mobile_use/tools/__init__.py
  • minitap/mobile_use/tools/mobile/__init__.py
  • minitap/mobile_use/utils/__init__.py
  • pyproject.toml

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

@plfavreau plfavreau closed this Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant