From: | "Jelte Fennema-Nio" <me(at)jeltef(dot)nl> |
---|---|
To: | "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | "Nazir Bilal Yavuz" <byavuz81(at)gmail(dot)com> |
Subject: | CI: Add task that runs pgindent |
Date: | 2025-10-21 12:19:29 |
Message-ID: | DDNZTVO6E6GF.17IEQGZ1GC9D7@jeltef.nl |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At PGConf.dev 2025 one thing that came up in the "Scaling PostgreSQL
Development" unconference session is that new hackers don't know all the
details of our development flow by heart yet. Of course it's documented
on the wiki, but even if they find the relevant wiki pages they often
still miss/forget things. One of the things they often forget is
formatting their code. The consensus at that session was that it was
probably worth adding a CI task for this to nudge newcomers to indent
their code.
We're not too worried about this new requirement scaring away newcomers,
since autoformatting has become fairly commonplace in open source
development. Also committers can of course still choose to format the
patch themselves before committing if the formatting is failing.
This might also help reduce the number of unindented commits that
committers push, which require a follow up "fix indent" commit to make
the koel buildfarm animal happy again.
Attachment | Content-Type | Size |
---|---|---|
v1-0001-CI-Add-task-that-runs-pgindent.patch | text/x-patch | 2.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2025-10-21 12:36:46 | Re: [PATCH] Remove make_temptable_name_n() |
Previous Message | Pavel Stehule | 2025-10-21 11:26:50 | Re: Add \pset options for boolean value display |