Feature and its Use Cases
Is your feature request related to a problem? Please describe.
As an umbrella organization managing almost 200 repositories across multiple GitHub spaces (AOSSIE-Org, StabilityNexus, DjedAlliance), tracking contributor activity—especially during the current GSoC period—is a monumental task. Mentors currently have to manually check individual repositories (like Agora-Blockchain, Devr.AI, EduAid, etc.) to see which applicants are making meaningful contributions.
Furthermore, relying on the standard GitHub REST API to fetch contributor stats across 60+ repositories requires dozens of sequential/parallel network requests. This creates massive frontend bottlenecks and quickly burns through the 5,000 req/hr PAT rate limit.
Describe the solution you'd like
I propose building a "Contributor Activity Matrix" view within OrgExplorer tailored specifically for mentors and org admins. Instead of fetching repository-by-repository, we migrate this specific data-fetching layer to the GitHub GraphQL API (v4) using the search query.
Technical Execution Plan:
- GraphQL
search Integration: Implement a single, highly optimized GraphQL request that fetches the latest PRs and Issues across the entire organization in O(1) network requests.
Example Query:
query getOrgWideActivity {
search(query: "org:AOSSIE-Org is:pr is:merged created:>2026-01-01", type: ISSUE, first: 100) {
nodes {
... on PullRequest {
repository { name }
author { login }
createdAt
url
}
}
}
}
Additional Context
No response
Code of Conduct
Feature and its Use Cases
Is your feature request related to a problem? Please describe.
As an umbrella organization managing almost 200 repositories across multiple GitHub spaces (
AOSSIE-Org,StabilityNexus,DjedAlliance), tracking contributor activity—especially during the current GSoC period—is a monumental task. Mentors currently have to manually check individual repositories (likeAgora-Blockchain,Devr.AI,EduAid, etc.) to see which applicants are making meaningful contributions.Furthermore, relying on the standard GitHub REST API to fetch contributor stats across 60+ repositories requires dozens of sequential/parallel network requests. This creates massive frontend bottlenecks and quickly burns through the 5,000 req/hr PAT rate limit.
Describe the solution you'd like
I propose building a "Contributor Activity Matrix" view within
OrgExplorertailored specifically for mentors and org admins. Instead of fetching repository-by-repository, we migrate this specific data-fetching layer to the GitHub GraphQL API (v4) using thesearchquery.Technical Execution Plan:
searchIntegration: Implement a single, highly optimized GraphQL request that fetches the latest PRs and Issues across the entire organization inO(1)network requests.Example Query:
Additional Context
No response
Code of Conduct