chore: configure CodeRabbit for Java 25/Spring Boot 4 project

[nanotaboada]

• Add comprehensive path-based review instructions for Java/Spring Boot architecture layers (controllers, services, repositories, models), test patterns, and infrastructure files
• Configure relevant tools (PMD, Gitleaks, Checkov, Hadolint) while disabling language-specific tools not applicable to Java projects
• Set project-specific filters, coverage threshold (80%), and enforce Conventional Commits format for PR titles

---

This change is 

Summary by CodeRabbit

Chores

• Updated code review configuration and tooling to better align with Java/Spring Boot best practices.
• Enabled expanded code quality and safety checks for more comprehensive reviews.
• Enhanced code generation guidance with Java-specific conventions and industry standards.
• Improved code review process with better support for conventional commits and documentation requirements.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@nanotaboada has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 55 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between a492176 and 088d856.

📒 Files selected for processing (1)

• .coderabbit.yaml

Walkthrough

The .coderabbit.yaml configuration file is updated to tailor CodeRabbit for a Java/Spring Boot project. Changes include enabling path-based review instructions across Java source locations, configuring tool coverage specific to Java, and establishing code generation and knowledge base guidelines aligned with Spring Boot conventions.

Changes

Cohort / File(s)

Summary

CodeRabbit Configuration \.coderabbit\.yaml

Enabled related_prs and suggested_labels in reviews; introduced path-based review instructions for Java/Spring Boot (controllers, services, repositories, models, tests) with coding style and DI expectations; added path_filters to exclude build/artifact directories; enhanced auto_review with WIP keywords and expanded base_branches; reconfigured tools section to enable Java-focused tools (PMD, gitleaks, semgrep, etc.) and disable others; updated code_generation with Javadoc/OpenAPI path_instructions and 80% test coverage targets; unified knowledge_base with Java patterns

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title follows the Conventional Commits format with 'chore:' prefix, is descriptive about the configuration changes for a Java/Spring Boot project, and is well under the 80-character limit at 61 characters.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-coderabbit-config

---

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

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (f0151c1)	55	55	100.00%
Head commit (088d856)	55 (+0)	55 (+0)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#249)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f0151c1) to head (088d856).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##              master      #249   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity        22        22           
===========================================
  Files              2         2           
  Lines             55        55           
  Branches           4         4           
===========================================
  Hits              55        55           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

.coderabbit.yaml (3)

60-66: Consider allowing JpaRepository as an alternative.

The instruction specifies CrudRepository<Entity, ID>, but JpaRepository (which extends CrudRepository) is more commonly used in Spring Data JPA projects as it provides additional methods like findAll() with sorting/paging and batch operations. Consider updating to accept both:

-        - Repositories should extend CrudRepository<Entity, ID>
+        - Repositories should extend CrudRepository or JpaRepository

---

162-165: Remove redundant case variant.

The ignore_title_keywords matching is case-insensitive per the schema, so "wip" is redundant when "WIP" is already specified.

Suggested fix

     ignore_title_keywords:
       - "WIP"
       - "DO NOT REVIEW"
-      - "wip"

---

288-295: Brace expansion in glob pattern may not work as expected.

The pattern **/*.{yml,yaml} uses brace expansion, which isn't universally supported across all glob implementations. Consider splitting into separate patterns for reliability:

Suggested fix

       - "**/Dockerfile"
-      - "**/*.{yml,yaml}"
+      - "**/*.yml"
+      - "**/*.yaml"
       - "**/*.sh"

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0151c1 and a492176.

📒 Files selected for processing (1)

• .coderabbit.yaml

⏰ Context from checks skipped due to timeout of 120000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

🔇 Additional comments (6)

.coderabbit.yaml (6)

148-158: LGTM!

The path filters appropriately exclude build artifacts (target/), database files, and Maven wrapper files from code review.

---

177-191: LGTM!

The pre-merge checks are well-configured with appropriate thresholds and Conventional Commits guidance for PR titles.

---

271-272: Note: LanguageTool disabled.

Disabling LanguageTool means grammar and style checking won't run on documentation and comments. If you want prose quality checks on Javadocs or markdown files, consider enabling it.

---

305-328: LGTM!

The code generation settings are well-configured with appropriate Javadoc guidelines and JUnit 5 test conventions. The 80% coverage target aligns with the docstrings threshold in pre-merge checks.

---

329-340: LGTM!

Issue enrichment is appropriately configured with auto-planning triggered by the "planning" label.

---

2-2: Java 25 (LTS) designation is correct. Oracle officially designated JDK 25 as an LTS release with general availability on September 16, 2025.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud