DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, 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:23:07 +0200	[thread overview]
Message-ID: <CAJFAV8wcEgvqdCiPefmxUSyP=QjfYoWiJ846EZKsDDnwa-b45g@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ynhCwV76W+1QVwDrzXFLiRWv+x9FiQkCGq+fw2f0CLJw@mail.gmail.com>

On Wed, 1 Oct 2025 at 16:12, David Marchand <david.marchand@redhat.com> wrote:
> On Wed, 1 Oct 2025 at 16:04, Burakov, Anatoly <anatoly.burakov@intel.com> wrote:
> > 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?
>
> The ovsrobot creates pull requests in its dpdk github repository, and
> Coderabbit and sourcery are invoked on them.
> Look for a link in patchwork, under the name "ci/github-robot-post".
>
> For example, this exact patch got a branch and pr in ovsrobot/dpdk:
> https://github.com/ovsrobot/dpdk/tree/series_36267
> https://github.com/ovsrobot/dpdk/pull/124

Btw, you'll notice a bit of noise, due to how the PR is created
against ovsrobot/main, and not the exact DPDK main branch at the
moment the patch is submitted on the ml.


-- 
David Marchand


      reply	other threads:[~2025-10-01 14:23 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
2025-10-01 14:12   ` David Marchand
2025-10-01 14:23     ` David Marchand [this message]

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='CAJFAV8wcEgvqdCiPefmxUSyP=QjfYoWiJ846EZKsDDnwa-b45g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=anatoly.burakov@intel.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).