chore: add coderabbit

[hamza221]

Inspired from https://github.com/nextcloud/mail/blob/main/.coderabbit.yaml

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI

[coderabbitai]

Warning

This pull request changes a CodeRabbit configuration file. Because it comes from a fork or its author is not a repository collaborator, reviews use only the configuration from the target branch. The proposed configuration will take effect after it is merged.

📝 Walkthrough

Walkthrough

Added a .coderabbit.yaml file for the Nextcloud Contacts repository. The configuration sets the review language and tone, enables assertive advisory reviews, disables automatic reviews and merge-blocking status, filters generated and bundled paths, disables PHPStan and PHPMD, and adds reviewer-only guidance for formatting and provenance findings.

Merge Risk: 🔵 Low · up to b898d

The new review configuration disables some status reporting but may leave other CodeRabbit statuses active, which could create unexpected checks or branch-protection interactions. The PR is mergeable with explicit owner confirmation or a follow-up configuration change.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: adding CodeRabbit configuration. It is concise and specific.
Description check	✅ Passed	The description is related to the changeset because it identifies the CodeRabbit configuration as inspired by another Nextcloud repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

---

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

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 8f4e71c7-9e08-48f1-abd1-d6265453c221

📥 Commits

Reviewing files that changed from the base of the PR and between 7d98902 and b898d9d.

📒 Files selected for processing (1)

• .coderabbit.yaml

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🔎 Supported by static analysis

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- .coderabbit.yaml ---'
cat -n .coderabbit.yaml
printf '%s\n' '--- repository references ---'
rg -n --hidden --glob '!node_modules' --glob '!dist' --glob '!build' \
  'review_status|review_progress|commit_status|request_changes_workflow|base_branches' . \
  | head -200 || true

Repository: nextcloud/contacts

Length of output: 3749

---

🌐 Web query:

CodeRabbit configuration reference review_status review_progress commit_status

💡 Result:

In the CodeRabbit configuration, specifically within the reviews section of a .coderabbit.yaml file, the options review_status, review_progress, and commit_status are used to control how CodeRabbit reports the status of AI-driven code reviews [1][2][3]. 1. review_status: This setting controls whether CodeRabbit posts canonical, user-facing review status messages, such as notifications for skipped reviews, in the pull request summary comment [1][2]. It defaults to true [1]. 2. review_progress: This setting enables the publication of progress updates for the review, typically reported via platform-native mechanisms like GitHub check runs or progress reports [1][2]. When enabled, CodeRabbit provides detailed tracking of the review process [1]. 3. commit_status: This setting allows CodeRabbit to mirror review progress using legacy commit statuses, which is useful for compatibility with required status checks and existing CI/CD automations [1][2]. According to documentation, this setting is primarily utilized when review_progress is disabled [1]. Additionally, there is a related setting fail_commit_status (often defaulting to false), which determines whether review errors should result in a failure of the active outward review status surface (either progress reporting or the legacy commit status) [1][2].

Citations:

• 1: https://docs.coderabbit.ai/reference/configuration
• 2: https://github.com/formbricks/formbricks/blob/main/.coderabbit.yaml
• 3: GitHub pull request 9 in Binitpyro/Personal_Memory_Assistant (link omitted to avoid creating a cross-reference)

---

Disable the remaining CodeRabbit status surfaces.

review_status: false disables review status messages, but review_progress remains enabled by default. commit_status is a separate legacy status surface. If branch protection requires a CodeRabbit status, set both to false or confirm that no such status is required.