Re: New year, new commitfest app improvements - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: New year, new commitfest app improvements
Date
Msg-id CAKFQuwZ0Jm00KuGU9suA0mtTUzQ9WcLiubPMcUJ_J7-ix_Dv-A@mail.gmail.com
Whole thread Raw
In response to Re: New year, new commitfest app improvements  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: New year, new commitfest app improvements
List pgsql-hackers
On Tuesday, January 13, 2026, Chao Li <li.evan.chao@gmail.com> wrote:

Suppose a patch has already created a CF entry, and a reviewer wants to suggest a code change and attaches a diff file in the thread. In that case, CI will automatically pick up the diff and run tests, which will very likely result in a CI failure. I’ve run into this situation myself; see [1].

Would it make sense for CI to only pick up .patch files and ignore .diff files? Or provide some way else to indicate CI to ignore certain emails?

Other ways exist:


Note the section on “what is considered a patch”.

There is definitely room for improved discoverability here though.

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Optimize LISTEN/NOTIFY
Next
From: Chao Li
Date:
Subject: Re: New year, new commitfest app improvements