Re: [PATCH] Addition of JetBrains project directory to .gitignore - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Addition of JetBrains project directory to .gitignore
Date
Msg-id 31772.1575385628@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Addition of JetBrains project directory to .gitignore  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: [PATCH] Addition of JetBrains project directory to .gitignore  (David Nedrow <dnedrow@me.com>)
Re: [PATCH] Addition of JetBrains project directory to .gitignore  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 3 Dec 2019, at 15:47, David Nedrow <dnedrow@me.com> wrote:
>> This patch simply adds “.idea/“ to the list of global excludes across all subdirectories. This directory is created
whena JetBrains IDE is used to open a project. In my specific case, Clion is creating the project directory. 
>>
>> The ONLY change in the patch is the “.idea/“ addition to .gitignore.

> -1.  This seems like something better suited in a local gitignore for those who
> use Jetbrains products. See the documentation for ~/.gitignore_global.

Yeah, we already have a policy that we won't add entries for, say,
editor backup files.  This seems like the same thing.  It's stuff
generated by a tool you use, and you'd need it for any project
you work on, so a personal ~/.gitexclude seems like the answer.

(Roughly speaking, I think the project policy is/should be that only
junk files created by application of build rules in our Makefiles
should be excluded by our own .gitexclude files.)

As a point of reference, I have

$ cat ~/.gitexclude
*~
*.orig

to suppress emacs backup files and patch backup files respectively.
Somebody who prefers another editor would have no use for *~.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Session WAL activity
Next
From: Mark Dilger
Date:
Subject: Re: Windows buildfarm members vs. new async-notify isolation test