Bug: contributors query doesn't seem to respect repository field

[sympatheticmoose]

Using the contributors query type, the results don't seem to change if you select different repositories within the organization.

[Tarasusrus]

I looked into this. The repository argument is actually wired through correctly — the query is repository(name: $name, owner: $owner) { mentionableUsers(...) }, so it is scoped to the selected repository at the GraphQL level.

The reason the results don't change between repositories in the same organization is that the Contributors query type is backed by mentionableUsers, not by actual repository contributors. mentionableUsers returns everyone who can be mentioned in the repo (largely org members with access), which is effectively uniform across repositories in one org. The code comment hints at this: "listing contributors (or rather, mentionable users in a repository)".

So this is less "repository is ignored" and more "the query returns mentionable users rather than real contributors". Fixing it to return actual per-repo contributors would mean switching to a different data source — e.g. the REST GET /repos/{owner}/{repo}/contributors endpoint (contributors ranked by commit count) or aggregating commit-history authors via GraphQL. That would change the output schema (REST contributors expose login + contribution count, not the current name/company/email fields), so it risks breaking existing dashboards.

Before I open a PR: would you prefer

1. keeping mentionableUsers but renaming/clarifying the query type, or
2. switching Contributors to real contributors (REST contributors endpoint), accepting the output-field change, or
3. adding a separate query type for real contributors and leaving the current one as-is (no regression)?

Happy to implement whichever direction you'd like.