From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: rjarry@redhat.com, Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [PATCH] ci: configure Coderabbit
Date: Wed, 1 Oct 2025 10:18:25 +0200 [thread overview]
Message-ID: <20251001081825.2638077-1-david.marchand@redhat.com> (raw)
Coderabbit currently runs in ovsrobot repository (and can be used in
public personal forks).
poems are funny, but not really helpful.
Reduce some noise by disabling (or collapsing) some verbose outputs.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
I copied the tone instructions and some settings from grout.
The docstrings check is noisy, and often wrong for C headers
(especially EAL arch headers).
Opinions?
---
.coderabbit.yaml | 14 ++++++++++++++
MAINTAINERS | 1 +
devtools/check-spdx-tag.sh | 2 +-
3 files changed, 16 insertions(+), 1 deletion(-)
create mode 100644 .coderabbit.yaml
diff --git a/.coderabbit.yaml b/.coderabbit.yaml
new file mode 100644
index 0000000000..7968f4f4ba
--- /dev/null
+++ b/.coderabbit.yaml
@@ -0,0 +1,14 @@
+language: "en-US"
+tone_instructions: "Only provide helpful, relevant comments. Be brief and terse but clear."
+reviews:
+ profile: "chill"
+ collapse_walkthrough: true
+ changed_files_summary: false
+ sequence_diagrams: false
+ suggested_labels: false
+ poem: false
+ finishing_touches:
+ docstrings:
+ enabled: false
+ unit_tests:
+ enabled: false
diff --git a/MAINTAINERS b/MAINTAINERS
index 1a2729be66..b82632fea3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -141,6 +141,7 @@ M: Aaron Conole <aconole@redhat.com>
M: Michael Santana <maicolgabriel@hotmail.com>
F: .github/workflows/build.yml
F: .ci/
+F: .coderabbit.yaml
Driver information
M: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
diff --git a/devtools/check-spdx-tag.sh b/devtools/check-spdx-tag.sh
index 984825026e..eb4a88a3fb 100755
--- a/devtools/check-spdx-tag.sh
+++ b/devtools/check-spdx-tag.sh
@@ -18,7 +18,7 @@ print_usage () {
no_license_list=\
':^.git* :^.mailmap :^.ci/* :^README :^*/README* :^MAINTAINERS :^VERSION :^ABI_VERSION '\
':^license/ :^config/ :^buildtools/ :^*.abignore :^*.cocci :^*/poetry.lock '\
-':^*/Kbuild :^kernel/linux/uapi/version '\
+':^*/Kbuild :^kernel/linux/uapi/version :^.coderabbit.yaml '\
':^*.ini :^*.data :^*.json :^*.cfg :^*.txt :^*.svg :^*.png'
check_spdx() {
--
2.51.0
reply other threads:[~2025-10-01 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251001081825.2638077-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=rjarry@redhat.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).