ci(github): exclude test files from mixed PR size calculation

[binbandit]

What Changed

• Switched PR size labeling from aggregate PR additions/deletions to per-file diff stats from the GitHub pull request files API.
• Excluded test-file line changes when a PR also changes non-test files.
• Preserved test-file line counting when a PR only changes tests.
• Added logging for test vs non-test lines and a warning when GitHub's file listing may truncate at 3,000 files.

Why

• Mixed PRs with substantial test updates were receiving inflated size labels even when the production-code review surface stayed small.
• Test-only PRs should still reflect their actual review size instead of collapsing to the smallest label.

Testing

• bun fmt
• bun lint
• bun typecheck
• Local scenario validation for mixed code+tests, test-only, browser-test, and apps/server/integration fixture changes.

Note

Exclude test files from PR size label calculation in mixed PRs

• Replaces the simple additions + deletions count from the event payload with a per-file aggregation using pulls.listFiles to detect and separate test vs. non-test changed lines.
• For mixed PRs (test + non-test files), size labels are based only on non-test changed lines; for test-only PRs, the full test line count is used.
• Test files are detected via a set of regex patterns applied per file in pr-size.yml.
• Action logs now report non-test lines, test lines, effective lines, and a classification category.
• Behavioral Change: PRs with test file changes alongside production code will now receive a smaller size label than before.

^{Macroscope summarized cfcbb25.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0e29351f-bbbc-4c04-af75-744e2bb44b75

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

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.}

[Noojuno]

This is obv up to Julius and Theo (and team), but if it were me I don't think I'd want this tbh. Tests still need to be reviewed, so if a PR adds a shitload of tests, the effort to review is still decently high, especially because of the crazy rate of shit and useless tests that LLM's love to write

[binbandit]

The problem is that a small change to add a tiny feature might need a whole new test file written. Tests are pretty effortless to review, but the actual implementation is more effort.

So we should base the "size" on the actual feature / fix being added, and not base it on the tests.

---

That being said, if the PR is to just add tests, then we will use that as a gauge for how large the PR is

[UtkarshUsername]

The problem is that a small change to add a tiny feature might need a whole new test file written.

I agree, because of this it would be better to exclude test files from the labels, when the PR is not only for tests.