Add a flag to ignore common usage patterns?

[al-the-x]

It's pretty common for me to drop a .gitignore file into a directory that I want to exist within the project but whose contents should always be ignored, e.g. the dist/ folder or other compilation destination. The patterns I use for that file are always:

*
.*
!.gitignore

Would it be worthwhile to have a flag for git ignore that would drop in one of these common usage patterns, at least as a starting point? For example:

$> cd dist
/path/to/my/project/dist/
$> git ignore --all
Adding patterns to: .gitignore
... adding *
... adding .*
... adding !.gitignore
$> cd ..
/path/to/my/project/
$> git status -s
??  dist/.gitignore

Happy to submit a PR and contribute, as well.

[al-the-x]

@Lee-W submitted a similar PR to what I was proposing but uses http://gitignore.io/ instead: #448 (great idea there), which was merged and released in 4.0.0. Thoughts on adding a --for flag to git-ignore that proxies git-ignore-io and --all for the pattern proposed?

$> cd dist
/path/to/my/project/dist/
$> git ignore --all
Adding patterns to: .gitignore
... adding *
... adding .*
... adding !.gitignore
$> cd ..
/path/to/my/project
$> git status -s
??   dist/.gitignore
$> git ignore --for jekyll
Fetching https://www.gitignore.io/api/jekyll ...
Adding patterns to: .gitignore
# Created by https://www.gitignore.io/api/jekyll

### Jekyll ###
_site/
.sass-cache/
.jekyll-metadata
$> git status -s
??    .gitignore
??    dist/.gitignore