add file TextFiles.gitattributes and add folder ".override/"

[ghost]

Hello, folks!

I found a closed issue here: github/alexkaratarakis/gitattributes/issues/176 with this old idea.

I would like to know if I've thought about creating a folder called ".override" to add .gitattributes files related to document files like txt, html, markdown, xml etc.

I find this idea interesting and would like to contribute, help.

Have you all ever thought of creating a folder called ".override" to add .gitattributes files related to document files like txt, html, xml, markdown?

This pull-request is the solution to this question. For example, here is a .gitattributes file where I have forced GitHub to count all Txt files towards my language stats, except for readme.md.

Use case: This is very interesting when you have a repository full of text files like blog posts or website content. And you want to show statistics in your repository related to the amount of text you've written. For this use case to be satisfied, it is necessary to use the .gitattributes file with these options configured;

filepath: .override/TextFiles.gitattributes

*.txt linguist-vendored=false
*.txt linguist-generated=false
*.txt linguist-documentation=false
*.txt linguist-detectable=true

why a folder called ".override/"?
The folder ".override" serves to separate source code file vs document file.

img-before

img-after

where did your idea come from?
I read these 3 links and did something based on it:

• Override languages being included by language statistics: Here is how to create a .gitattributes file with override.
• Markdown language is not detected: Here it says why files in md, txt format are ignored in the count.
• How to Get Github to Recognize a Pure Markdown Repo: Here it teaches step by step how to create a .gitattributes file with override and why it works.

[Richienb]

The reason for using ,override folder could be better justified.
I think we could just store them in the root, though I'm not sure about that either.