Enhance title matching strategy in labeler.yml

[ReneWerner87]

Summary by CodeRabbit

• Chores
  • Updated repository ignore rules to exclude IDE-specific workspace files from version control. This reduces noise in commits, prevents accidental inclusion of local environment artifacts, and keeps the repository cleaner.
  • Improves developer experience with cleaner diffs and more focused code reviews.
  • No changes to application behavior or public interfaces.
  • Streamlines collaboration by ensuring consistent project state across contributors without local tool configuration files being tracked.

[gemini-code-assist]

Summary of Changes

Hello @ReneWerner87, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the automated labeling process by introducing a more robust title matching strategy within the .github/labeler.yml configuration. The changes aim to improve the accuracy of label assignments by distinguishing between conventional commit prefixes and general keywords, ensuring that titles with explicit prefixes are correctly categorized while still allowing for flexible keyword-based matching when no such prefix is present. Additionally, it includes a minor update to the .gitignore file to exclude IDE-specific files.

Highlights

• Enhanced Title Matching Strategy: The title matching logic in .github/labeler.yml has been significantly improved to prioritize conventional commit prefixes (e.g., docs:, fix:) and then fall back to colon-safe free-text keyword matching. This ensures more accurate label assignments.
• Updated Label Regular Expressions: Regular expressions for 'Documentation', 'Bug', 'Updates', 'Dependencies', 'Feature', 'Proposal', and 'Question' labels have been updated to incorporate the new matching strategy and expand keyword recognition.
• Added .gitignore Entry: The .gitignore file now includes an entry to ignore IntelliJ IDEA project files (.idea/**), preventing them from being committed.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .github/labeler.yml
  • Introduced a new title matching strategy that prioritizes conventional commit prefixes (e.g., feat:, fix:) and then falls back to colon-safe free-text keyword matching.
  • Updated regular expressions for 'Documentation', 'Bug', 'Updates', 'Dependencies', 'Feature', 'Proposal', and 'Question' labels to incorporate the new strategy and expand keyword recognition.
  • Added inline comments explaining the new title regex concept and strategy.
• .gitignore
  • Added .idea/** to the ignore list.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request significantly enhances the title matching strategy for the labeler by adopting a two-pronged approach: it prioritizes conventional commit prefixes and falls back to keyword matching on the title part before a colon. This makes the labeling much more precise. The addition of .idea/** to .gitignore is also a good practice. I've suggested a couple of minor refinements to the new regular expressions to make them even more precise by replacing broad \w* wildcards with more specific suffix matching. Overall, this is a great improvement.

[Copilot]

Pull request overview

This pull request enhances the title matching strategy in the shared labeler configuration for the gofiber organization. The changes improve how pull requests and issues are automatically labeled based on their titles by implementing a sophisticated two-alternative regex strategy that prioritizes conventional commit prefixes while still supporting free-text keyword matching.

Changes:

• Enhanced regex patterns for all label matchers to support conventional commits format (with scope and breaking change indicators)
• Restricted free-text keyword matching to only the portion of the title before the first colon, preventing unintended label matches when conventional commit prefixes are used
• Added comprehensive documentation comments explaining the matching strategy
• Added .gitignore entry for IntelliJ IDEA configuration files

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
.gitignore	Added .idea/** to ignore IntelliJ IDEA configuration directory
.github/labeler.yml	Enhanced all label matcher regexes to support conventional commits format and restrict free-text matching to prevent conflicts when conventional prefixes are used

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Walkthrough

The pull request adds a single ignore rule to .gitignore, excluding JetBrains IDE workspace directories (.idea/**) from version control. This prevents IDE-specific files and configurations from being tracked in the repository.

Changes

Cohort / File(s)	Summary
IDE Configuration Exclusion .gitignore	Added pattern .idea/** to ignore JetBrains IDE workspace files and directories.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A speck of ignoring, so clean and so neat,
IDE files tucked away, a rabbit's retreat,
No .idea folders shall clutter the flow,
Just git and good code, as codebases grow!
hops happily ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title mentions enhancing title matching strategy in labeler.yml, but the only actual change is adding .idea/** to .gitignore, which is unrelated to the title's claim.	Update the title to accurately reflect the change: 'Add .idea directory to .gitignore' or similar, matching the actual changeset.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 improve_labeling

---

No actionable comments were generated in the recent review. 🎉

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38329eb and 9dd64e3.

⛔ Files ignored due to path filters (1)

• .github/labeler.yml is excluded by !**/*.yml

📒 Files selected for processing (1)

• .gitignore

🔇 Additional comments (2)

.gitignore (2)

1-1: The .idea/** pattern is correct.

The pattern correctly excludes JetBrains IDE workspace files from version control, which is a standard best practice.

---

1-1: PR title accurately reflects the changes.

The commit adds both .github/labeler.yml (with enhanced title matching strategies) and .gitignore (with IDE exclusions) as stated in the commit message. This is an initial repository setup that creates the centralized workflow configuration structure for the gofiber organization, including the labeler.yml file mentioned in the PR title.

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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