Best way to use .gitattributes with a documentation project #7834
Unanswered
mtgstuber
asked this question in
Classification
Replies: 1 comment
-
|
The following |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi folks,
I have a project whose main delivery is a specification (geisa/specification). Most of the project is restructured text files (.rst) or scalable vector graphics (.svg). When github runs linguist it classifies the project as being a combination of mermaid and python, which are really incidental to the project overall. I completely appreciate that for normal coding projects ignoring the documentation files is the correct behavior. In this case, the project is documentation. What's the best way to use .gitattributes to get the languages block to better reflect the nature of the project?
If I set linguist-documentation=false and set .rst to linguist-detectable, would the language stats for the project count the RST files?
Beta Was this translation helpful? Give feedback.
All reactions