DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Cc: <rjarry@redhat.com>, Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] ci: configure Coderabbit
Date: Wed, 1 Oct 2025 16:03:22 +0200	[thread overview]
Message-ID: <9acb2557-1f42-4880-ba93-020b14e6a0f5@intel.com> (raw)
In-Reply-To: <20251001081825.2638077-1-david.marchand@redhat.com>

On 10/1/2025 10:18 AM, David Marchand wrote:
> 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?
> 
> ---

Hi David,

Can you provide a little more details on what exactly you are proposing?

On the back of this patch, I installed CodeRabbit in my IDE (VSCode), 
and did a review of one of my recent patchsets - it's quite interesting, 
actually, and the comments provided were basic but meaningful, alas the 
free version is limited to like 1 review per 30 minutes or something so 
it's a bit limiting. On top of that, I found the tool a lot more usable 
than GitHub Copilot reviews, which are attached to GH pull requests 
rather than Git branches, and they take a lot less time to boot, so I 
feel like this tool has potential.

That said, I'm not sure what this patch is supposed to do - is it to 
have it set up to review patches automatically?

-- 
Thanks,
Anatoly

  reply	other threads:[~2025-10-01 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  8:18 David Marchand
2025-10-01 14:03 ` Burakov, Anatoly [this message]
2025-10-01 14:12   ` David Marchand
2025-10-01 14:23     ` David Marchand

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=9acb2557-1f42-4880-ba93-020b14e6a0f5@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=aconole@redhat.com \
    --cc=david.marchand@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).