ci: Add configuration for CodeRabbit

[vojtechtrefny]

We want to disable some features and tell it to ignore some files.

Summary by CodeRabbit

• Chores
  • Updated development tool configuration to optimize code review workflows.

---

Note: This release contains infrastructure changes with no direct impact on end-user functionality.

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

[coderabbitai]

Walkthrough

A new .coderabbit.yaml configuration file is added to define CodeRabbit settings, including language preference (en-US), review profile (chill), feature toggles, path filters for review scope, and chat configuration options.

Changes

Cohort / File(s)	Summary
Configuration Addition \.coderabbit\.yaml	New CodeRabbit configuration file with language set to en-US, early_access disabled, review profile set to chill with multiple feature toggles disabled, path filters excluding plans, .github, and .fmf directories, and chat.art disabled

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Configuration file contains only static settings with no complex logic or interdependencies to verify
• Changes are straightforward key-value pairs with clear intent

Pre-merge checks and finishing touches

✅ 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 a CodeRabbit configuration file with the 'ci:' prefix appropriately indicating a CI/configuration-related change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

[gemini-code-assist]

Summary of Changes

Hello @vojtechtrefny, 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 establishes the initial configuration for CodeRabbit, a code review automation tool, within the project's continuous integration setup. The primary goal is to tailor CodeRabbit's behavior by disabling certain features and defining specific file paths to be ignored, ensuring that the automated reviews are more focused and relevant to the core codebase changes.

Highlights

• CodeRabbit Configuration Added: Introduced a new ".coderabbit.yaml" file to configure the CodeRabbit integration within the CI pipeline.
• Feature Disablement: Disabled several CodeRabbit review features, including poems, in-progress fortunes, sequence diagrams, related issues/PRs, and suggested labels/reviewers, to streamline the review process.
• Path Filtering Implemented: Configured CodeRabbit to ignore specific directories ("plans/", ".github/", and ".fmf/**") from its review scope, focusing its analysis on relevant code changes.

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 introduces a configuration file for CodeRabbit to customize its behavior, such as disabling certain features and ignoring specific file paths. The configuration is a good step towards tailoring the CI process. I've found a small potential issue in the path_filters configuration that might not behave as expected. I've included a specific suggestion to align it with the likely intent.

[gemini-code-assist]

The path filter !.fmf/** seems to target a directory named .fmf. However, looking at the files in the repository, .fmf appears to be a file extension (e.g., plans/tests.fmf). To ignore all files with the .fmf extension, a glob pattern matching the extension would be more appropriate. While !plans/** already covers the current .fmf files, using !**/*.fmf would be more precise and robust for any future .fmf files added outside the plans directory.

  path_filters: ["!plans/**", "!.github/**", "!**/*.fmf"]

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.coderabbit.yaml (1)

1-14: Configuration is valid and aligns with PR objectives.

All settings comply with the CodeRabbit schema. The YAML syntax is correct, and the configuration appropriately disables non-essential features (poems, fortune messages, diagrams, suggestions) and filters out CI, workflow, and metadata files from review scope. The "chill" profile setting pairs well with the reduced feature set for focused code reviews.

Consider adding inline YAML comments to document the rationale behind disabled features and excluded directories, improving clarity for future maintainers:

  language: "en-US"
  early_access: false
  reviews:
    profile: "chill"
+   # Disable decorative/non-essential features for focused reviews
    poem: false
    in_progress_fortune: false
    sequence_diagrams: false
    related_issues: false
    related_prs: false
    suggested_labels: false
    suggested_reviewers: false
+   # Exclude CI/workflow files and project metadata from review scope
    path_filters: ["!plans/**", "!.github/**", "!.fmf/**"]
  chat:
+   # Disable ASCII/emoji art in chat responses
    art: false

📜 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 5198b86 and 8df7df9.

📒 Files selected for processing (1)

• .coderabbit.yaml (1 hunks)

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

• GitHub Check: testing-farm:fedora-43-x86_64
• GitHub Check: testing-farm:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: testing-farm:fedora-43-x86_64:revdeps
• GitHub Check: testing-farm:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: unit-tests
• GitHub Check: static-analysis