Re: Add trim_trailing_whitespace to editorconfig file
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Daniel Gustafsson <daniel@yesql.se>,
Melanie Plageman <melanieplageman@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-04T15:23:28Z
Lists: pgsql-hackers
On 04.04.24 16:58, Jelte Fennema-Nio wrote:
> On Thu, 4 Apr 2024 at 15:25, Peter Eisentraut<peter@eisentraut.org> wrote:
>> Everybody has git. Everybody who edits .gitattributes can use git to
>> check what they did.
> What CLI command do you use to fix/ gitattributes on all existing
> files? Afaict there's no command to actually remove the trailing
> whitespace that git add complains about. If you don't have such a
> command, then afaict updating gitattributes is also essentially
> blind-updating.
I don't have a command to fix files automatically, but I have a command
to check them:
git diff-tree --check $(git hash-object -t tree /dev/null) HEAD
That's what I was hoping for for editorconfig-check, but as I said, the
experience wasn't good.
Commits
-
Add script to keep .editorconfig in sync with .gitattributes
- 2452e71ff2fe 18.0 landed
-
Remove non-existing file from .gitattributes
- 1d577f2eaa88 15.7 landed
- 2c7f2eb0c8aa 16.3 landed
- e85732dac0e9 17.0 landed