Add badges to README (tests, Java, LeetCode) – Issue #7

[HoudaBelhad]

This pull request adds the following badges to the README:

• Test badge to show build/test status
• Java version badge
• LeetCode solutions badge

The badges are displayed at the top of the README for better visibility.

This addresses issue #7.

Summary by CodeRabbit

• Documentation

  • Added project status badges to the README for CI, Java version, and LeetCode visibility.

• Chores

  • Configured automated continuous integration to run builds and tests on pushes and pull requests, with Java build tooling and caching enabled.

[coderabbitai]

Warning

Rate limit exceeded

@HoudaBelhad has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 18 minutes and 28 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.

Walkthrough

Adds a GitHub Actions CI workflow that runs on push and PRs to main using JDK 21 and Maven tests, and inserts three status/reference badges (Tests, Java, LeetCode) at the top of the README.

Changes

Cohort / File(s)	Summary
CI/CD Setup ​.github/workflows/ci.yml	Adds a GitHub Actions workflow triggered on push and pull_request to main: checks out code, sets up Temurin JDK 21, enables Maven caching, and runs mvn -B test.
Documentation README.md	Prepends three badges (CI/Tests, Java, LeetCode) to the README header.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Add Javadoc generation and dependency review to CI #4: Modifies the same GitHub Actions workflow, replacing mvn -B test with mvn -B verify and adding javadoc and dependency-review steps.

Poem

🐰 A tiny hop, a steady build,
Badges gleam atop the hill,
JDK set, tests run true,
Pipelines hum — we’re good to chew! 🥕✨

🚥 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 title clearly and concisely summarizes the main change: adding three badges (tests, Java, LeetCode) to the README. It is specific, accurate, and directly reflects the primary objective documented in the PR.
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

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@README.md`:
- Line 3: Replace the hardcoded static badge image string
("![Tests](https://img.shields.io/badge/tests-passing-brightgreen)") with a
dynamic GitHub Actions workflow status badge: use the actions badge URL pattern
for your repo and workflow file
(https://github.com/<owner>/<repo>/actions/workflows/<workflow_file>.yml/badge.svg)
and update the markdown to link the badge to the workflow run page
(https://github.com/<owner>/<repo>/actions/workflows/<workflow_file>.yml) and
adjust alt text (e.g., "Tests") so the README shows real CI status instead of
always "passing".

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

1-24: CI workflow structure looks good overall.

Standard setup with proper checkout, JDK setup, Maven caching, and batch-mode test execution. A couple of observations:

1. Java version mismatch with project guidelines: The project's build guidelines specify Java 25 (LTS), but this workflow uses JDK 21. If the project has moved to Java 25, update accordingly:

   -        java-version: '21'
   +        java-version: '25'

2. Consider pinning action versions to full SHAs for supply-chain security (optional for a personal repo).

Based on learnings: "Build project with Java 25 (LTS) version."

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Tests badge is static and will always show "passing" regardless of actual CI status.

Since this PR also adds a GitHub Actions CI workflow, use the dynamic workflow status badge instead of a hardcoded static one. The current badge is misleading — it will still show "passing" even when the build is broken.

Proposed fix: use a dynamic GitHub Actions status badge

-![Tests](https://img.shields.io/badge/tests-passing-brightgreen)
+[![Tests](https://github.com/yamcodes/leetcode-solutions-java/actions/workflows/ci.yml/badge.svg)](https://github.com/yamcodes/leetcode-solutions-java/actions/workflows/ci.yml)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	
	[](https://github.com/yamcodes/leetcode-solutions-java/actions/workflows/ci.yml)

🤖 Prompt for AI Agents

In `@README.md` at line 3, Replace the hardcoded static badge image string
("![Tests](https://img.shields.io/badge/tests-passing-brightgreen)") with a
dynamic GitHub Actions workflow status badge: use the actions badge URL pattern
for your repo and workflow file
(https://github.com/<owner>/<repo>/actions/workflows/<workflow_file>.yml/badge.svg)
and update the markdown to link the badge to the workflow run page
(https://github.com/<owner>/<repo>/actions/workflows/<workflow_file>.yml) and
adjust alt text (e.g., "Tests") so the README shows real CI status instead of
always "passing".

[yamcodes]

Thanks @HoudaBelhad, Looks generally very good! Couple small notes, and please resolve conflicts so we can get this PR ready to merge!

[yamcodes]

(Nit) I would use the official LeetCode shields.io logo, either:

Suggested change

	
	

or

Suggested change

	
	

[yamcodes]

This file already exists on main, but according to the PR it's being "added".
This usually happens when branching off an outdated branch,

Could you please rebase or merge the latest main into your branch and resolve the conflict? That should remove this file from the diff.

[yamcodes]

Suggested change

	
	

We have already updated to Java 25 (latest LTS)