Add Codacy config to exclude test/ from analysis - #45
Conversation
Python test harness files under test/ were generating Codacy issues that don't apply to production extension code.
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe change updates Codacy exclusions and configures the Docker image to run PostgreSQL as the non-root ChangesRepository configuration
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Up to standards ✅🟢 Issues
|
f6c28e6 to
aeadd3f
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Dockerfile`:
- Line 21: Update the Dockerfile’s USER postgres configuration so
docker-entrypoint.sh starts with root privileges and can repair ownership of
mounted PGDATA or /var/lib/postgresql directories; only switch to postgres after
this initialization via a privileged wrapper if needed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 697201db-1fa1-4908-ae10-912cc586bf9f
📒 Files selected for processing (2)
.codacy.ymlDockerfile
🚧 Files skipped from review as they are similar to previous changes (1)
- .codacy.yml
aeadd3f to
93db25c
Compare
Run container as postgres user instead of root Add USER postgres to the Dockerfile after the build steps, which still need root to install into the PostgreSQL lib/share dirs. Exclude docker/** from Codacy: that image is a CI-only SSH test harness whose sshd requires root.
93db25c to
9254ec6
Compare
Python test harness files under test/ were generating Codacy issues that don't apply to production extension code.