Re: New year, new commitfest app improvements
| От | Chao Li |
|---|---|
| Тема | Re: New year, new commitfest app improvements |
| Дата | |
| Msg-id | A39099A5-E88A-4C2A-9F90-BBFCC16E3156@gmail.com обсуждение исходный текст |
| Ответ на | Re: New year, new commitfest app improvements ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Список | pgsql-hackers |
> On Jan 14, 2026, at 10:51, David G. Johnston <david.g.johnston@gmail.com> wrote: > > 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 filein the thread. In that case, CI will automatically pick up the diff and run tests, which will very likely result in aCI 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 CIto 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. > Good to learn. Using a “nocfbot” prefix should perfectly work. Best regards, -- Chao Li (Evan) HighGo Software Co., Ltd. https://www.highgo.com/
В списке pgsql-hackers по дате отправления: