Skip to content

test(git): add coverage for git_explain.git subprocess wrappers - #33

Merged
nazarli-shabnam merged 2 commits into
mainfrom
test/git-module-coverage
Jul 25, 2026
Merged

test(git): add coverage for git_explain.git subprocess wrappers#33
nazarli-shabnam merged 2 commits into
mainfrom
test/git-module-coverage

Conversation

@nazarli-shabnam

Copy link
Copy Markdown
Owner

Summary

  • git_explain/git.py (repo-root detection, staged/unstaged/untracked change parsing, rename/copy normalization, diff assembly) had zero test coverage.
  • Added tests/test_git.py covering repo-root/inside-repo checks, repo_has_commits, staged/unstaged/untracked detection, rename normalization, non-ASCII paths, and the combined-diff / diff-for-paths output shapes, using real git repos in tmp_path (same pattern as tests/test_run_apply.py).
  • Note: copy detection is exercised as "shows up as two separate adds" rather than a C status, since get_staged_changes() calls git diff --name-status without -C, so git never actually reports copies through that path today (only renames, which are detected by default in modern git).

Test plan

  • pytest -q
  • ruff check . / ruff format --check .

Closes #17

(Re-opened as a new PR: the original PR #25 was auto-closed by GitHub when main's history was rewritten to correct a contributor's commit attribution — this branch is unchanged.)

git.py parses raw git diff/ls-files output (including rename
normalization) but had no tests. Cover repo-root/inside-repo checks,
staged/unstaged/untracked detection, rename normalization, non-ASCII
paths, and the combined-diff / diff-for-paths output shapes.

Closes #17
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nazarli-shabnam, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e4cd46ef-7bb1-4fa0-9608-cef3e0f66eab

📥 Commits

Reviewing files that changed from the base of the PR and between 11a379a and c55ca93.

📒 Files selected for processing (3)
  • .github/workflows/ci.yml
  • pyproject.toml
  • tests/test_git.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch test/git-module-coverage

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

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

The lint job's `pip install ruff` had no version pin, decoupled from
pyproject.toml's own ruff>=0.8.0. A newer ruff release enables new
default-on lint rules, breaking CI on pre-existing code unrelated to
this change. Pin to the last known-good version in both places.
@nazarli-shabnam nazarli-shabnam self-assigned this Jul 25, 2026
@nazarli-shabnam
nazarli-shabnam merged commit 27e73ba into main Jul 25, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No test coverage for git.py

1 participant