Re: CI: Add task that runs pgindent

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Subject: Re: CI: Add task that runs pgindent
Date: 2025-10-21 16:09:01
Message-ID: 500982.1761062941@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jelte Fennema-Nio <me(at)jeltef(dot)nl> writes:
> On Tue, 21 Oct 2025 at 16:40, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So I think there is plenty of room for workflows where the committer
>> is expected to reindent just before commit.

> Interesting, but yeah that makes sense.

Also, it's far from un-heard-of to actually make two separate
commits, so that the mechanical-reindenting step can be put
into .git-blame-ignore-revs. I had a recent example at
80aa9848b/73873805f/db6461b1c.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Borisov 2025-10-21 16:17:00 Optimization of the is_normalized() function.
Previous Message Tom Lane 2025-10-21 16:02:27 Re: Client-only Meson Build From Sources