Horton
Menu

Re: run pgindent on a regular basis / scripted manner

Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

View thread
From: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2023-01-24T15:03:51Z
Lists: pgsql-hackers 
Andres> Of course, but I somehow feel a change of formatting should be
reviewable to
Andres> at least some degree

One way of reviewing the formatting changes is to compare the compiled
binaries.

If the binaries before and after formatting are the same, then there's a
high chance the behaviour is the same.

Vladimir

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix comment from commit 22655aa231.

  2. Add a few recent commits to .git-blame-ignore-revs.

  3. Pre-beta2 mechanical code beautification.

  4. Pre-beta mechanical code beautification.

  5. Make agreed-on updates in perltidy options.

  6. Remove obsolete pgindent options --code-base and --build

  7. Integrate pg_bsd_indent into our build/test infrastructure.

  8. Sync pg_bsd_indent's copyright notices with Postgres practice.

  9. Import pg_bsd_indent sources.

  10. pgindent: filter files for the --commit option

  11. pgindent: more ways to find files to indent

  12. Fix pgindent --show-diff option.

  13. Add non-destructive modes to pgindent

  14. Initial pgindent run with pg_bsd_indent version 2.0.