Please list all .gitattributes linguist-language= entries in the statistics, no matter what language name

[ell1e]

Select Topic Area

Product Feedback

Body

One of the repositories I have mirror of on github has this breakdown shown on here:

This breakdown is wrong. The source copy of the repository on Codeberg.org shows the following:

As you can see, Github is by about 80% off from the correct numbers. And the reason for that error is that Github ignores line 3 and line 4 in the .gitattributes file:

From a user perspective, there is no sane reason to behave like this that I'm aware of. Instead, the UI should actually list all linguist-language=... entries in the statistics, no matter what language names.

Why this is great:

• It doesn't harm anybody to show the correct stats.¹ Ideally the user's code stats offered via GraphQL should also include these custom entries.
• This would be great for DSLs² where for many the inherent point is them being project-specific, making it unfeasible to add them to Github's regular site-wide detection.
• This is great for hobbyist language designers and compiler makers where the project is too small to be added to Github's regular side-wide detection.

This is not a request for:

• I'm not suggesting to add arbitrary new made-up language names to the global code search outside of a project.
• I'm not suggesting Github should do anything else to accommodate such unknown and potentially made up entries, like any sort of syntax lighting.

Footnotes

1. If you're concerned about somebody using some naughty word as a language entry, I could also just add a file with naughty words into the repo regularly. Therefore, this shouldn't really be a concern more than it already is. ↩

2. Domain-specific languages. ↩

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐