search

toptal / gitignore.io

Create useful .gitignore files for your project
https://www.toptal.com/developers/gitignore
MIT License
8.25k stars 624 forks source link

Enhancement suggestion: distinguishing environment- and project-specific gitignore #446

Open TonalidadeHidrica opened 5 years ago

TonalidadeHidrica commented 5 years ago

My idea is about enhancement of the gitignore.io website: highlighting environment-specific items in the search box.

It is widely known that it is bad habit to add OS-specific / editor-specific / IDE-specific gitignore list into each project's .gitignore. Instead, one should add them into global .gitignore in their local machine. This is already pointed out in some issues, e.g. #4 , #38 . And in documentation it is already (implicitly) recommended to add Operating System and IDE settings to global .gitignore. However, since I have used the web interface only for a long time and didn't know it was not preferable; I just obediently followed to the message "Search Operating Systems, IDEs, or programming languages" and copy & pasted all the stuff into .gitignore in my each project. So my opinion is that it would be helpful (especially for beginners!) if the web interface highlighted Windows, Vim or Eclipse with yellow background when they were entered into the search box, and show humble warning message below. Is it difficult to do that? I'm sorry if this sort of issue was already posted.

joeblau commented 5 years ago

Great suggestion. I do have a few questions about how users would know what the yellow background would actually mean. Also it's the web so anything is possible — Right now I'm using the Select2 select box framework so if this functionality is available there, I could apply it to the gitignore.io.

TonalidadeHidrica commented 5 years ago

My general idea is something like the following. Here, I didn't edit the source code but just edited DOM with the dev tools.
I took casual glance at the documentation of Select2 and couldn't find the way to set the color for each item. Instead, adding an event listener for the change and adding some highlight class to the li element will probably do, although I'm not sure it's the best way. image

joeblau commented 5 years ago

Have you thought about his this may also apply to the command line?

TonalidadeHidrica commented 5 years ago

I didn't think of it but that sounds also useful. Maybe showing message to stderr or something?

ChaerilM commented 2 years ago

got a company repo filled with .nano_history, .bash_history, etc. this idea would be a nice thing to have

github-actions[bot] commented 2 years ago

This issue is stale because it has been open for 30 days with no activity.