chore(Makefile): add clean target to remove tools and coverage files

[flc1125]

Summary by CodeRabbit

• Chores
  • Added a new clean target to the Makefile for removing build artifacts and coverage files
  • Improved Makefile formatting with a minor newline addition

[coderabbitai]

Walkthrough

The pull request introduces a new clean target in the Makefile, designed to remove the tools directory and clean up coverage-related files. This addition provides a standardized method for clearing out generated files and temporary artifacts during the development process. The change includes marking the target as phony and ensures proper cleanup of coverage files like coverage.txt, coverage.out, and coverage.html.

Changes

File	Change Summary
Makefile	Added clean phony target for removing tools directory and coverage files

Poem

🐰 A Rabbit's Cleanup Rhyme 🧹

With a swish and a sweep, my Makefile's neat
Cleaning coverage files, a tidy treat
Phony target springs to life with glee
Wiping traces, setting artifacts free
A developer's delight, so clean and bright!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3ec6c48 and 30c464f.

📒 Files selected for processing (1)

• Makefile (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: go test (1.23.x, ubuntu-latest)
• GitHub Check: go test (1.22.x, ubuntu-latest)

🔇 Additional comments (2)

Makefile (2)

147-148: LGTM! Improved readability.

The added newline improves readability by properly separating Make targets.

---

149-152: LGTM! Well-implemented clean target.

The clean target is properly implemented with:

• Correct PHONY declaration
• Comprehensive cleanup of both tools and coverage files
• Silent operation with @rm
• Proper use of Makefile variables

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.34%. Comparing base (3ec6c48) to head (30c464f).
Report is 1 commits behind head on 4.x.

Additional details and impacted files

@@           Coverage Diff           @@
##              4.x     #191   +/-   ##
=======================================
  Coverage   94.34%   94.34%           
=======================================
  Files          11       11           
  Lines         690      690           
=======================================
  Hits          651      651           
  Misses         36       36           
  Partials        3        3           

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