Github dashboard misguiding

[HariVeeraVenkat]

Select Topic Area

Question

Body

Git-hub is a good platform to save projects without spoiling. But on seeing dashboard, it shows the wrong content.

• Ex:- I created a react project, so as we expected it shows JS project but it was shown CSS.
• It was a disappointment to see Logic code as Styling code.

Is this a bug or any other else.

[ARC7666]

It’s not a bug, but a common issue with how GitHub detects the main language of a repository.

GitHub uses a tool called Linguist to analyze your repo and decide what language is most dominant — based on the number of lines of code and file types. If your project has more .css or .html lines than .js or .jsx, it might classify the repo as CSS.

Let's fix it ->
1. Make sure your main code files (.js, .jsx, etc.) are committed and not ignored.
2. You can manually override the language by creating a .gitattributes file in the root of your repo with this line:
*.css linguist-detectable=false (This tells GitHub to ignore .css files when detecting the language.)
3.After committing that, GitHub may take a few minutes to update the language on the dashboard.

[117ABHISHEK]

🧩 Yeah, I’ve faced this too, especially with React projects where there's a good chunk of styling or HTML markup. It feels wrong when the logic-heavy repo is labeled as “CSS.”

Thanks to @ARC7666 for that solid tip, GitHub uses Linguist, and it's based on file size and line count, not just file type importance.

Here’s what worked for me:

✅ I added a .gitattributes file like this:

*.css linguist-detectable=false
*.html linguist-detectable=false

That shifted the focus back to the actual JavaScript and JSX code.

🔍 GitHub could really improve this by giving developers more control over how the language is detected or weighted — maybe even a setting in the repo config.

Until then, .gitattributes is our fix.

[Sumit262601]

Ever had your React repo show up as mostly “CSS” on GitHub? Yeah, same here — super frustrating when the bulk of your work is logic-heavy JS and JSX, not styles or markup.

Thanks to @ARC7666 for the insight: GitHub uses Linguist, which detects language based on file size and line count, not just by file type importance.

Here’s what fixed it for me:

✅ I added a .gitattributes file to my root directory with this:

*.css linguist-detectable=false *.html linguist-detectable=false

This made GitHub focus on what really matters — the JavaScript/JSX code.

🔍 Would be awesome if GitHub gave us more control, like repo-level settings to weight language detection better.

Until then, .gitattributes is our go-to fix. Happy coding!

[HariPasapuleti]

#166136

Why github labels your project weirdly

Even you poured your heart into a slick React app, only for GitHub to slap a big CSS label on the repo? Yeah, it's annoying. Here what's actually going on -- and what you can do about it.

How GitHub see your code

• GitHub donsen't get context.
• It uses a tool called Linguist.
• More lines = more weight.

What really happening?

• Language tages are just guesses.
• GitHub doesn't know which files matter.

How to set the record straight

Possible to make GitHub see things from your side? Here's a quick fix:

1. Add a .gitattributes file to your repo.
2. Drop in these lines:

* .css linguist-detectable=false

3. Commit and Push
4. Wait a minute.

[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. ⭐