The current logic seems to imply that a project has at least one git repo. Which is not always the case: some projects create software which is composed by multiple components which each are in a separate code repositories which all could be rather considered subprojects. For reasons like size of repo, build time (on CI) or enforced decoupling. Or where being part of the same project is rather for synergy in manpower, knowledge exchange, promo, release management etc. on organization level, not in code.
So those projects share mailinglist, wiki pages, irc channels, but all their multiple code repos could be considered subprojects, where the separate repo-centric reports (like builds, commits) make sense.

Examples:

• Calligra (which is a set of libs, plugins & apps, currently randomly distributed over 5 repos)
• KDevelop (abstract app platform, actual KDevelop program, plugins separated in different repos)

Proposed instant fix: Show reports also for project without a git repo (if anything else is configured)

While perhaps the project model needs an overhaul in general (something to be tackled on global KDE scale, as those wrong assumptions are reflected in many places), for the start it would be nice if reports.kde.org would still show all other reports for a project, even if no git repo is listed. After all one can be configure mailinglist, wikis etc. even when no git repo is set, so it is more surprising to see them not displayed on the resulting report page, but just a list of any subprojects.