Add .gitattributes file for project - #974
Merged
Merged
Conversation
IMHO it's useful to see Markdown files as one of the types of files listed on the GitHub front page in the file statistics section, alongside other files. It gives a sense for the amount of documentation present in a project. On the other hand, some configuration files are not useful to count, such as .md files in a `.gemini/` subdirectory and configuration files for tools like git.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request adjusts GitHub's file statistics by adding a .gitattributes file. The change makes Markdown files count towards language statistics and excludes various configuration files. My review identifies an opportunity to simplify the configuration by removing redundant overrides for files that GitHub's Linguist already excludes by default. This will improve the maintainability of the .gitattributes file.
Cross-checked this with the languages.yml file in the Linguist source code repo.
mhucka
changed the title
.gitattributes file for project
pavoljuhas
approved these changes
Jan 5, 2026
mhucka
added a commit
to mhucka/qsim
that referenced
this pull request
Jan 18, 2026
IMHO it's useful to see Markdown files as one of the types of files listed on the GitHub front page in the file statistics section, alongside other files. It gives a sense for the amount of documentation present in a project. On the other hand, some configuration files are not useful to count, such as .md files in a `.gemini/` subdirectory and configuration files for tools like git.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
IMHO it's useful to see Markdown files as one of the types of files listed on the GitHub front page in the file statistics section, alongside other files. It gives a sense for the amount of documentation present in a project.
On the other hand, some configuration files are not useful to count, such as .md files in a
.gemini/subdirectory and configuration files for tools like git.