Add "Development Tooling" section and refine auto-labeling

[snovak7]

Closes #36

Summary by CodeRabbit

• Chores
  • Updated release drafting configuration to introduce a new "Development Tooling" category.
  • Consolidated and expanded file labeling for development tooling and configuration files.
  • Streamlined label assignments by merging related configuration files under a single label.

[coderabbitai]

Walkthrough

The .github/release-drafter.yml file was updated to introduce a new "Development Tooling" category and consolidate autolabeler logic. The "area/dev-tooling" label is now applied to a broader set of configuration and project files, replacing several previous dependency-related labels and expanding file pattern coverage.

Changes

Cohort / File(s)	Change Summary
Release Drafter Configuration .github/release-drafter.yml	Added "Development Tooling" category; updated autolabeler to expand "area/dev-tooling" coverage and consolidate labels; removed separate dependency labels and adjusted file patterns.

Sequence Diagram(s)

Not applicable: No new feature or control flow logic introduced.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Consolidate autolabeling for Development Tooling files (#36)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Poem

A rabbit with a coder’s grin,
Tidied labels, grouped them in—
Tooling files now neatly tagged,
Old dependencies un-bagged.
With configs gathered, patterns wide,
Our burrow’s order multiplied!
🧑🏼‍💻🐇

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

---

📜 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 8e5b4a0 and 375d843.

📒 Files selected for processing (1)

• .github/release-drafter.yml (2 hunks)

🔇 Additional comments (2)

.github/release-drafter.yml (2)

32-34: LGTM! Well-structured category addition.

The new "Development Tooling" category is properly structured and uses an appropriate emoji and label naming convention that aligns with the consolidation objectives.

---

54-63: Excellent consolidation of development tooling files.

The autolabeler configuration effectively consolidates various development-related files under a single "area/dev-tooling" label. The file patterns comprehensively cover key development configuration files including GitHub workflows, editor configs, build properties, and package management files.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 36-consolidate-development-tooling-autolabeling

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @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.