| 1 |
On 12 Aug 2015 18:27, Brian Dolbec wrote: |
| 2 |
> 2) There is another alternate location that you can define files to |
| 3 |
> ignore locally without having to commit them to .gitignore. |
| 4 |
> Consider .gitignore a global setting. There is another setting |
| 5 |
> inside .git/info/exclude which is a local config file that will persist |
| 6 |
> and not be affected by pulls. |
| 7 |
> |
| 8 |
> So please use that for local exclusions you want to add and not try to |
| 9 |
> force them into a global .gitignore which is part of the repo. |
| 10 |
> Something that seems to be hotly debated. ;) |
| 11 |
|
| 12 |
as i stated, there's no reason for these paths to ever be committed. |
| 13 |
conversely, some people (not unreasonably so) will place files in there |
| 14 |
that have historically had known meanings. adding these to the global |
| 15 |
gitignore is simply the right thing to do and negatively impacts no one. |
| 16 |
-mike |
Archives