File tree Expand file tree Collapse file tree 2 files changed +33
-3
lines changed Expand file tree Collapse file tree 2 files changed +33
-3
lines changed Original file line number Diff line number Diff line change @@ -85,9 +85,6 @@ src/test/buildenv.py
85
85
# Resources cpp
86
86
qrc_ * .cpp
87
87
88
- # Qt creator
89
- * .pro.user
90
-
91
88
# Mac specific
92
89
.DS_Store
93
90
build
Original file line number Diff line number Diff line change @@ -171,3 +171,36 @@ Threads
171
171
- BitcoinMiner : Generates bitcoins (if wallet is enabled).
172
172
173
173
- Shutdown : Does an orderly shutdown of everything.
174
+
175
+ Ignoring IDE/editor files
176
+ --------------------------
177
+
178
+ In closed-source environments in which everyone uses the same IDE it is common
179
+ to add temporary files it produces to the project-wide ` .gitignore ` file.
180
+
181
+ However, in open source software such as Bitcoin Core, where everyone uses
182
+ their own editors/IDE/tools, it is less common. Only you know what files your
183
+ editor produces and this may change from version to version. The canonical way
184
+ to do this is thus to create your local gitignore. Add this to ` ~/.gitconfig ` :
185
+
186
+ ```
187
+ [core]
188
+ excludesfile = /home/.../.gitignore_global
189
+ ```
190
+
191
+ (alternatively, type the command ` git config --global core.excludesfile ~/.gitignore_global `
192
+ on a terminal)
193
+
194
+ Then put your favourite tool's temporary filenames in that file, e.g.
195
+ ```
196
+ # NetBeans
197
+ nbproject/
198
+ ```
199
+
200
+ Another option is to create a per-repository excludes file ` .git/info/exclude ` .
201
+ These are not committed but apply only to one repository.
202
+
203
+ If a set of tools is used by the build system or scripts the repository (for
204
+ example, lcov) it is perfectly acceptable to add its files to ` .gitignore `
205
+ and commit them.
206
+
You can’t perform that action at this time.
0 commit comments