You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if onefetch could parse .gitattributes and respect linguist-documentation rules.
E.g: onefetch believes that a project of mine (ANESE) is written primarily in assembly, when it's actually written entirely in C++. This is most likely caused by the large collection of .asm test files included in the repo.
Github allows marking directories / files as documentation (not code) via the linguist-documentation attribute in a repo's .gitattributes file.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
It would be nice if onefetch could parse
.gitattributes
and respectlinguist-documentation
rules.E.g: onefetch believes that a project of mine (ANESE) is written primarily in assembly, when it's actually written entirely in C++. This is most likely caused by the large collection of .asm test files included in the repo.
Github allows marking directories / files as documentation (not code) via the
linguist-documentation
attribute in a repo's.gitattributes
file.See http://schacon.github.io/git/gitattributes.html and https://www.rubydoc.info/github/github/linguist for details.
The text was updated successfully, but these errors were encountered: