👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
I had no idea there was a cli, I always just use CURL. I generally use pretty similar .gitignore's depending on the type of project that I am working on.
I keep this one as a shell alias
alias ignore='curl https://www.gitignore.io/api/vim,node,data,emacs,python,pycharm,executable,sublimetext,visualstudio,visualstudiocode > .gitignore'
Sure - I get that. There's a purpose for that ~/.git directory in addition to .gitignore on individual projects. The latter is useful if you ever work with anyone else, which is where this config and tool come in...
Each developer on a project can have a different IDE and it is unnecessary to accumulate it in one .gitignore. The third solution is the global .gitignore.
I usually use my own Makefile to handle the project on local machine.
Different strokes, I suppose. There are absolutely some files that are regularly .gitignoreed that are independent of IDE.
node_modules/ forel example, and often there are .env.something files with varying names depending on the project type.
I'm sure you've experienced this in varying degrees throughout your career - there's rarely a clear-cut, single answer to anything we do. I'm not sure it benefits anyone much to world such a broad cudgel as to call a tool like this unhelpful because of your preference.
I'd imagine we could think of a dozen other reasons for and against this over a coffee. Maybe we will get to one day!
I'm a Senior DevOps Architect and publish most of my projects as open source. I have a wife, a son and a real life in Hamm, Germany. In my part-time I enjoy making games, music and acting. (He/him)
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
Of course not, but it definitely helps smooth out the workflow now. You also benefit from the work of the community this put this together - which is one of the things I really love about open source software. If you feel particularly strongly about the way you organized your .gitignore files in the past, why not submit your work as a pull request?
I had no idea there was a cli, I always just use CURL. I generally use pretty similar
.gitignore's depending on the type of project that I am working on.I keep this one as a shell alias
It's just a shell script, but working at function level.
I do this quite often.
You can't misspell, though. For example, it must be
nodenotnode.jsornodejs.I don't want to distribute a list of my private files and directories in project to other developers. I save my settings to
.git/info/excludeSure - I get that. There's a purpose for that
~/.gitdirectory in addition to.gitignoreon individual projects. The latter is useful if you ever work with anyone else, which is where this config and tool come in...Each developer on a project can have a different IDE and it is unnecessary to accumulate it in one
.gitignore. The third solution is the global.gitignore.I usually use my own
Makefileto handle the project on local machine.Different strokes, I suppose. There are absolutely some files that are regularly
.gitignoreed that are independent of IDE.node_modules/forel example, and often there are.env.somethingfiles with varying names depending on the project type.I'm sure you've experienced this in varying degrees throughout your career - there's rarely a clear-cut, single answer to anything we do. I'm not sure it benefits anyone much to world such a broad cudgel as to call a tool like this unhelpful because of your preference.
I'd imagine we could think of a dozen other reasons for and against this over a coffee. Maybe we will get to one day!
Awesome, definitely going to use it.
Sweet! I'd love to hear what you think. It's been super useful to me.
Awesome. Thanks for pointing that out. I didn't know about that tool.
Glad you found it helpful!
Thanks for the catch, fixed it
cool, i didn't know this exist.
This tool does not invalidate all the manual guess work that was done before this existed!
Of course not, but it definitely helps smooth out the workflow now. You also benefit from the work of the community this put this together - which is one of the things I really love about open source software. If you feel particularly strongly about the way you organized your .gitignore files in the past, why not submit your work as a pull request?
IntelliJ (or any jet brains product) already does that for you.
Always more than one way to skin a cat!