Add PR Size Checker That Warns on Large Diffs and Fails on Very Large Diffs

[vjuliaife]

Description:
Large pull requests are harder to review thoroughly and more likely to introduce undetected bugs, yet TariffShield has no guardrail to discourage oversized changes. A PR size checker that warns when a diff exceeds 400 lines and fails CI when it exceeds 1000 lines nudges contributors to split work into reviewable chunks, improving review quality and reducing merge risk.

Acceptance Criteria:

• Create .github/workflows/pr-size.yml that triggers on pull_request (types: opened, synchronize, reopened) and counts the total lines added plus removed using git diff --stat against the PR base SHA
• If the diff is between 400 and 999 lines, post a PR comment via actions/github-script warning "This PR is large (N lines). Consider splitting it into smaller PRs for easier review." and set the step outcome to neutral (do not fail)
• If the diff is 1000 lines or more, post a PR comment explaining the hard limit and fail the workflow step so the size check becomes a blocking status check
• Exclude auto-generated files from the line count: package-lock.json, Cargo.lock, *.snap test snapshots, and any file under dist/ or target/ are excluded via a .prsize-ignore file at the repo root using the same glob format as .gitignore
• The size thresholds (400 warn, 1000 fail) are configurable via workflow env variables PR_SIZE_WARN and PR_SIZE_FAIL so they can be adjusted without editing workflow logic
• If an oversized PR has a large-pr-approved label applied by a maintainer, the size check is bypassed — allowing emergency large changes with explicit sign-off
• Document the PR size policy in CONTRIBUTING.md under "Pull Request Guidelines" with guidance on how to split a large feature into smaller PRs

Relevant Files:

• .github/workflows/pr-size.yml — new PR size check workflow
• .prsize-ignore — glob patterns for files excluded from line count
• CONTRIBUTING.md — contributor guide (add PR size policy section)

[drsteinerdj]

Submitted PR #414 for this: #414

It adds the PR size workflow, .prsize-ignore, warning/failure thresholds, the large-pr-approved bypass, and CONTRIBUTING documentation.

[josephamly36-commits]

@josephamly36-commits has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer,
I would like to work on this issue. I am a full stack developer I have experience working with JavaScript, Python, C++, and Rust, with a primary focus on frontend development using React, Next.js, and TypeScript.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @josephamly36-commits to this issue.

[abayomiwav]

@abayomiwav has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

please assign me this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abayomiwav to this issue.

[drips-wave]

Congratulations, @abayomiwav! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @abayomiwav: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @abayomiwav as part of the Stellar Wave Program's 7th Wave 🥳

😎 @abayomiwav: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.