| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | Jelte Fennema-Nio <me(at)jeltef(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New year, new commitfest app improvements |
| Date: | 2026-01-14 02:51:48 |
| Message-ID: | CAKFQuwZ0Jm00KuGU9suA0mtTUzQ9WcLiubPMcUJ_J7-ix_Dv-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, January 13, 2026, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)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:
https://wiki.postgresql.org/wiki/Cfbot
Note the section on “what is considered a patch”.
There is definitely room for improved discoverability here though.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-01-14 02:55:08 | Re: New year, new commitfest app improvements |
| Previous Message | Tom Lane | 2026-01-14 02:44:57 | Re: Optimize LISTEN/NOTIFY |