I’m working on a C++ project that uses the Qt framework and I have it hosted on GitHub. The issue I’m facing is that GitHub is automatically detecting the wrong programming language for my repository.
The problem occurs because Qt projects include .pro files (like MyApp.pro) which GitHub incorrectly identifies as Prolog files instead of part of a C++ project. This confusion is affecting the language statistics for my repo.
Is there a way to inform GitHub that these .pro files should be considered related to C++ and not Prolog? I want my repository to accurately display as a C++ project in the language breakdown.
I hit this same problem migrating Qt projects to GitHub. The .gitattributes fix works, but you can also use linguist-detectable=false for files that shouldn’t count toward language detection at all. Qt projects have tons of .ui forms and .qrc resource files that mess with detection too. Try adding *.pro linguist-language=QMake to your .gitattributes file - it’s more accurate since .pro files are actually QMake project files. Don’t expect instant results though. GitHub usually takes up to 24 hours to recalculate the language stats after you push.
u can fix that by adding a .gitattributes in ur repo root. just put *.pro linguist-language=C++ in it. this will let GitHub know the .pro files r C++ not prolog. it works great for Qt stuff!
GitHub’s language detection relies on the Linguist library, which can indeed misinterpret files in Qt projects. The suggested solution of using .gitattributes is effective, but consider also the linguist-vendored option for files that don’t impact your language statistics. I faced similar issues with embedded projects where certain files were misclassified. Be mindful that any modifications to .gitattributes will only take effect on future commits, so a new push is necessary for the updates to reflect in the language statistics, which may take a few hours.
i tried using a .gitignore before but it didn’t help with stats. the .gitattributes fix is def the way to go. my qt app had similar probs - it took like 12 hrs for gitHub to update after pushin the fix. just remember to commit the .gitattributes right or it won’t do anything.