From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, Jelte Fennema-Nio <me(at)jeltef(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: CI: Add task that runs pgindent |
Date: | 2025-10-21 14:10:15 |
Message-ID: | CAN55FZ1htZTESmDZu4VFek-zz1Z09j4swdHX_Z2V1zLau26W5g@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Tue, 21 Oct 2025 at 16:46, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 21 Oct 2025, at 15:39, Florents Tselai <florents(dot)tselai(at)gmail(dot)com> wrote:
> >
> > That wouldn’t preclude having a CI task as well, of course.
> > The hook would mainly help contributors catch formatting issues locally, while the CI task would serve as a failsafe for committers.
>
> One common argument against enforcing proper indentation in submissions is that
> it adds a barrier to entry,
I think this patch targets two type of people, those who know how to run CI but:
1- Do not know how to run indentation checks
2- Forgot to run indentation checks
For #1, perhaps we could print a note suggesting people check
"src/tools/pgindent/README" when formatting fails. This might help
lower the barrier. Though it is possible it could raise it instead, I
am not entirely sure.
For #2, I think this patch is clearly helpful. We can discuss if it is
worth it to spend CI credits, though.
--
Regards,
Nazir Bilal Yavuz
Microsoft
From | Date | Subject | |
---|---|---|---|
Next Message | Aya Iwata (Fujitsu) | 2025-10-21 14:14:34 | RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE |
Previous Message | Dimitrios Apostolou | 2025-10-21 13:57:31 | Re: [PATCH v4] parallel pg_restore: avoid disk seeks when jumping short distance forward |