Re: run pgindent on a regular basis / scripted manner
| От | Tom Lane |
|---|---|
| Тема | Re: run pgindent on a regular basis / scripted manner |
| Дата | |
| Msg-id | 2620572.1697503500@sss.pgh.pa.us обсуждение |
| Ответ на | Re: run pgindent on a regular basis / scripted manner (Peter Geoghegan <pg@bowt.ie>) |
| Ответы |
Re: run pgindent on a regular basis / scripted manner
Re: run pgindent on a regular basis / scripted manner Re: run pgindent on a regular basis / scripted manner |
| Список | pgsql-hackers |
Peter Geoghegan <pg@bowt.ie> writes:
> There were two independent fixup commits to address complaints from
> koel just today (from two different committers). Plus there was a
> third issue (involving a third committer) this past Wednesday.
> This policy isn't working.
Two thoughts about that:
1. We should not commit indent fixups on behalf of somebody else's
misindented commit. Peer pressure on committers who aren't being
careful about this is the only way to improve matters; so complain
to the person at fault until they fix it.
2. We could raise awareness of this issue by adding indent verification
to CI testing. I hesitate to suggest that, though, for a couple of
reasons:
2a. It seems fairly expensive, though I might be misjudging.
2b. It's often pretty handy to submit patches that aren't fully
indent-clean; I have such a patch in flight right now at [1].
2b could be ameliorated by making the indent check be a separate
test process that doesn't obscure the results of other testing.
regards, tom lane
[1] https://www.postgresql.org/message-id/2617358.1697501956%40sss.pgh.pa.us
В списке pgsql-hackers по дате отправления: